From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patchwork [-rcu,1/1] rcu: fix rcu CONFIG logic
Date: Fri, 29 Apr 2011 09:03:22 +0800 [thread overview]
Message-ID: <4DBA0E5A.2090905@cn.fujitsu.com> (raw)
In-Reply-To: <BANLkTikoT4vHDjeNpoVWzefqMRBFAC0unA@mail.gmail.com>
On 04/28/2011 07:17 PM, Sedat Dilek wrote:
> Hi Lai Jiangshan,
>
> I like this patch (with explanations) and would test it, against which
> (GIT) tree is this for?
>
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/kfree_rcu
>
>
> [1] https://patchwork.kernel.org/patch/735291/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2011-04-29 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 11:17 Patchwork [-rcu,1/1] rcu: fix rcu CONFIG logic Sedat Dilek
2011-04-29 1:03 ` Lai Jiangshan [this message]
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=4DBA0E5A.2090905@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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