From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Paul Menage" <menage@google.com>,
balbir@linux.vnet.ibm.com, serue@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [-mm] Add an owner to the mm_struct (v9)]
Date: Tue, 15 Apr 2008 00:06:46 +0300 [thread overview]
Message-ID: <84144f020804141406n7ffd8a89ld1008afc1d541640@mail.gmail.com> (raw)
In-Reply-To: <20080414123624.0635798d.akpm@linux-foundation.org>
On Mon, Apr 14, 2008 at 10:36 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> > > Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
> >
> > Reviewed-by: Paul Menage <menage@google.com>
> >
> > I'm still not sure when to use Acked-by versus Reviewed-by - is it
> > just based on the level of scrutiny/review?
>
> Yes. Reviewed-by: is a lot stronger that Acked-by:. I've seen some pretty
> shocking Acked-by:'s :)
Heh, I hope mine wasn't one. But the point here is that, no, I didn't
review the patch that closely (it's mostly cgroup stuff anyway) but I
do want to see struct mm_struct ->owner in the kernel for revoke thus
Acked-by.
next prev parent reply other threads:[~2008-04-14 21:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 14:13 Balbir Singh
2008-04-14 14:49 ` Pekka Enberg
2008-04-14 16:04 ` Paul Menage
2008-04-14 19:36 ` Andrew Morton
2008-04-14 21:06 ` Pekka Enberg [this message]
2008-04-15 0:07 ` Andrew Morton
2008-04-15 17:13 ` Oleg Nesterov
2008-04-15 18:13 ` Paul Menage
2008-04-15 19:59 ` Oleg Nesterov
2008-04-17 3:38 ` Balbir Singh
2008-04-17 11:30 ` Oleg Nesterov
2008-04-17 16:34 ` Paul Menage
2008-04-17 16:19 ` Oleg Nesterov
2008-04-17 17:40 ` Balbir Singh
2008-04-17 17:08 ` Oleg Nesterov
2008-04-17 17:50 ` Paul Menage
2008-04-17 19:07 ` Balbir Singh
2008-04-17 17:49 ` Paul Menage
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=84144f020804141406n7ffd8a89ld1008afc1d541640@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=serue@us.ibm.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®