From: Paul Menage <menage@google.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make cgroup_path() RCU-safe
Date: Wed, 17 Dec 2008 00:01:05 -0800 [thread overview]
Message-ID: <6599ad830812170001wfca7cd0n15e5ead3a569f2c2@mail.gmail.com> (raw)
In-Reply-To: <494852FA.3000101@cn.fujitsu.com>
On Tue, Dec 16, 2008 at 5:16 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>
> But the patch is word wrapped..
Sigh. I thought that I'd fixed gmail to not do that ...
I'll try to resend.
>
> We already have kernel-doc for cgroup_path(), why do we need those comments
> in cgroup.h.
>
Fair point - I got rid of those extra comments.
Paul
next prev parent reply other threads:[~2008-12-17 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 23:58 Paul Menage
2008-12-17 1:16 ` Li Zefan
2008-12-17 8:01 ` Paul Menage [this message]
2008-12-17 9:11 ` Li Zefan
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=6599ad830812170001wfca7cd0n15e5ead3a569f2c2@mail.gmail.com \
--to=menage@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
/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®