From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Jiri Kosina <jkosina@suse.cz>,
Dmitry Torokhov <dtor@insightbb.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Fix use-after-free oops in Bluetooth HID.
Date: Sat, 7 Jul 2007 12:27:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707071222480.31544@woody.linux-foundation.org> (raw)
In-Reply-To: <1183834720.3066.83.camel@shinybook.infradead.org>
On Sat, 7 Jul 2007, David Woodhouse wrote:
>
> When cleaning up HIDP sessions [...]
Thanks.
> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Btw, and totally unrelated to the patch itself..
I changed that second "Signed-off-by:" into an "Acked-by:", since that
more accurately reflects what happened.
Not that it really matters, but it's nice to see what chain the patch
actually took (from you to me - sign-off path), and independently of that
see who looked at it and approved it (acked-by), and then often we
additionally end up having a set of people who might have tested it
("Tested-by:") or maybe should just have been aware of it (the "Cc:")
ones.
So the "Signed-off-by:" thing is one of many possible thigns that you can
do, but it's somewhat special in that it has some "legal" meaning in that
it is supposed to show the people who either wrote it or who forwarded it
(possibly with changes, but quite often just unchanged).
Linus
next prev parent reply other threads:[~2007-07-07 19:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 16:45 [1/2] 2.6.22-rc7: known regressions Michal Piotrowski
2007-07-03 17:29 ` Sparc32: random invalid instruction occourances on sparc32 (sun4c) Mark Fortescue
2007-07-03 18:57 ` [PATCH] " Mark Fortescue
2007-07-03 19:26 ` David Woodhouse
2007-07-03 21:25 ` Mark Fortescue
2007-07-03 21:56 ` David Woodhouse
2007-07-03 22:47 ` Mark Fortescue
2007-07-03 23:36 ` David Woodhouse
2007-07-04 3:27 ` Mark Fortescue
2007-07-04 3:33 ` David Woodhouse
2007-07-04 10:27 ` Mark Fortescue
2007-07-04 14:46 ` David Woodhouse
2007-07-04 18:38 ` Mark Fortescue
2007-07-03 21:41 ` David Miller
2007-07-03 22:01 ` David Woodhouse
2007-07-03 17:50 ` [1/2] 2.6.22-rc7: known regressions Bartlomiej Zolnierkiewicz
2007-07-03 23:09 ` David Chinner
2007-07-05 0:20 ` David Woodhouse
2007-07-05 1:26 ` [PATCH 2.6.22 REGRESSION] Fix slab redzone alignment David Woodhouse
2007-07-05 1:42 ` [1/2] 2.6.22-rc7: known regressions David Woodhouse
2007-07-05 16:28 ` Linus Torvalds
2007-07-05 16:43 ` David Woodhouse
2007-07-05 18:46 ` David Woodhouse
2007-07-05 19:31 ` David Woodhouse
2007-07-05 19:51 ` Linus Torvalds
2007-07-05 21:03 ` Dmitry Torokhov
2007-07-06 22:50 ` Jiri Kosina
2007-07-07 0:33 ` Dmitry Torokhov
2007-07-07 1:05 ` Jiri Kosina
2007-07-07 1:28 ` David Woodhouse
2007-07-07 2:25 ` David Woodhouse
2007-07-07 18:28 ` Marcel Holtmann
2007-07-07 18:36 ` Linus Torvalds
2007-07-07 18:58 ` [PATCH] Fix use-after-free oops in Bluetooth HID David Woodhouse
2007-07-07 19:27 ` Linus Torvalds [this message]
2007-07-09 2:32 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.999.0707071222480.31544@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=michal.k.k.piotrowski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®