From: Andrew Morton <akpm@linux-foundation.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: paulmck@linux.vnet.ibm.com, mingo@elte.hu,
linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
tglx@linutronix.de, viro@zeniv.linux.org.uk,
benh@kernel.crashing.org, paulus@samba.org, sparse@chrisli.org
Subject: Re: [GIT PULL] rcu: finalize debugobjects, first round of RCU sparse pointer checks
Date: Wed, 2 Jun 2010 08:52:54 -0700 [thread overview]
Message-ID: <20100602085254.778aaf31.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100602192749.F512.A69D9226@jp.fujitsu.com>
On Wed, 2 Jun 2010 19:34:41 +0900 (JST) KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > Hello, Ingo,
> >
> > Here are the final commits from Mathieu's debugobjects series and the
> > first few from Arnd's RCU-pointer sparse series. The first three remove
> > RCU's (useless) initializations from mm, fs, and powerpc:
> >
> > mm: http://lkml.org/lkml/2010/5/18/562
> > fs: http://lkml.org/lkml/2010/5/18/500
> > powerpc:http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg43510.html
> >
> > Kosaki Motohiro agreed that the mm patch should go up -tip, and none of
> > the other maintainers objected to the prospect of their patches going
> > up -tip.
>
> Andrew, can we hear your opinion? I think this patch series have some
> dependencies, then -tip is best place. If any code confliction occur,
> I promise I'll solve it soon.
>
A wee little two-line patch? Go wild!
next prev parent reply other threads:[~2010-06-02 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 16:50 [GIT PULL] rcu: finalize debugobjects, first round of RCU sparse pointer checks Paul E. McKenney
2010-06-02 10:34 ` KOSAKI Motohiro
2010-06-02 15:52 ` Andrew Morton [this message]
2010-06-03 3:58 ` KOSAKI Motohiro
2010-06-08 18:07 ` Ingo Molnar
2010-06-08 18:37 ` Ingo Molnar
2010-06-08 18:51 ` Paul E. McKenney
2010-06-08 19:07 ` Ingo Molnar
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=20100602085254.778aaf31.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=benh@kernel.crashing.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=sparse@chrisli.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).