From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mathieu.desnoyers@polymtl.ca, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/6] Linux Kernel Markers - Architecture Independent Code
Date: Thu, 6 Sep 2007 16:37:37 -0700 [thread overview]
Message-ID: <20070906163737.9cc91307.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070906160429.629c9497.akpm@linux-foundation.org>
On Thu, 6 Sep 2007 16:04:29 -0700 Andrew Morton wrote:
> > On Thu, 6 Sep 2007 16:00:01 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > On Thu, 06 Sep 2007 16:07:34 -0400 Mathieu Desnoyers wrote:
> >
> > > Changelog:
> > > - markers_mutex now nests inside module_mutex rather than the opposite.
> > >
> > > Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> > > Reviewed-by: Christoph Hellwig <hch@infradead.org>
> > > Reviewed-by: Rusty Russell <rusty@rustcorp.com.au>
> > > Reviewed-by: "Frank Ch. Eigler" <fche@redhat.com>
> >
> > Documentation/SubmittingPatches recognizes Signed-off-by: and
> > Acked-by:. Nothing about Reviewed-by. Quote:
> >
> > Acked-by: is not as formal as Signed-off-by:. It is a record that the acker
> > has at least reviewed the patch and has indicated acceptance.
> >
> > Reviewed-by: carries no such connotation or indication IMO.
> > Please use Acked-by if that's what these reviewers have done.
>
> Yeah. We will start introducing Reviewed-by: (I haven't yet quite worked
> out how yet) but it will be a quite formal thing and it would be something
> which the reviewer explicitly provided. For now, let's please stick with
> acked-by (if those individuals did indeed send an acked-by)
> -
Thanks. I look forward to the explanation of Reviewed-by, what it
means, and how it differs from Acked-by.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-09-06 23:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 20:07 [patch 0/6] Linux Kernel Markers for 2.6.23-rc4-mm1 Mathieu Desnoyers
2007-09-06 20:07 ` [patch 1/6] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-09-06 23:00 ` Randy Dunlap
2007-09-06 23:04 ` Andrew Morton
2007-09-06 23:37 ` Randy Dunlap [this message]
2007-09-07 4:05 ` Valdis.Kletnieks
2007-09-07 4:11 ` Randy Dunlap
2007-09-07 16:04 ` Theodore Tso
2007-09-07 17:10 ` Valdis.Kletnieks
2007-09-07 19:31 ` Christoph Hellwig
2007-09-07 21:30 ` Roland Dreier
2007-09-07 13:01 ` Mathieu Desnoyers
2007-09-06 20:07 ` [patch 2/6] Linux Kernel Markers - Add kconfig menus for the marker code Mathieu Desnoyers
2007-09-06 23:35 ` Randy Dunlap
2007-09-12 14:54 ` Mathieu Desnoyers
2007-09-06 20:07 ` [patch 3/6] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-09-06 23:48 ` Randy Dunlap
2007-09-06 20:07 ` [patch 4/6] Linux Kernel Markers - Documentation Fix Mathieu Desnoyers
2007-09-06 20:07 ` [patch 5/6] Port of blktrace to the Linux Kernel Markers Mathieu Desnoyers
2007-09-06 20:07 ` [patch 6/6] Linux Kernel Markers - Port SPU to markers Mathieu Desnoyers
2007-09-08 7:04 ` Alexey Dobriyan
2007-09-08 7:23 ` Mathieu Desnoyers
2007-09-08 12:11 ` Christoph Hellwig
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=20070906163737.9cc91307.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
/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