From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: upcoming percpu changes
Date: Fri, 12 Feb 2010 22:23:34 +0900 [thread overview]
Message-ID: <4B755656.7000904@kernel.org> (raw)
In-Reply-To: <20100212221058.37b7c6e6.sfr@canb.auug.org.au>
Hello,
On 02/12/2010 08:10 PM, Stephen Rothwell wrote:
> A good start would be commit d3f5fa4075414c7754126fbdc7c8fbd3906db7c8
> ("percpu: add __percpu sparse annotations to net"). You would need to
> rebase it on top of net-next and note that "struct macvlan_dev" has been
> moved to include/linux/if_macvlan.h. Then just send it to DaveM.
>
> You could also send commit e20b68160144bcacbde008b9cf7df4e1544b2507
> ("percpu: add __percpu sparse annotations to net drivers") along with it.
>
> Commit 949c49c93a02b62278a63457d0d3192d66e55105 ("percpu: add __percpu
> sparse annotations to x86") can just go to the x86 guys and commit
> 0b6dd45041220083a3692edae5253c35d19bcb2b ("percpu: add __percpu sparse
> annotations to hw_breakpoint") to Frederic Weisbecker.
>
> Commit eeb721be6bc03fe37755e69ab5c3ba2fe9897fd9 ("percpu: add __percpu
> sparse annotations to trace") needs rebasing onto the tip perf/core
> branch and then could be sent to Steve and co.
>
> That takes care of most of it and the rest, as you say, we can sort out
> if it becomes a problem.
The changes being basically trivial, it doesn't seem to bring much
benefit but yeah sure I can send those chunks to the maintainers.
Thanks.
--
tejun
prev parent reply other threads:[~2010-02-12 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 5:16 upcoming percpu changes Stephen Rothwell
2010-02-05 5:48 ` Tejun Heo
2010-02-05 7:09 ` Ingo Molnar
2010-02-05 7:31 ` Tejun Heo
2010-02-05 7:29 ` Ingo Molnar
2010-02-12 8:21 ` Tejun Heo
2010-02-12 11:10 ` Stephen Rothwell
2010-02-12 13:23 ` Tejun Heo [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=4B755656.7000904@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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).