From: Steven Rostedt <rostedt@goodmis.org>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>,
akpm@linuxfoundation.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [guv 04/16] core: Convert __get_cpu_var uses
Date: Mon, 26 Aug 2013 11:31:34 -0400 [thread overview]
Message-ID: <20130826113134.5306379d@gandalf.local.home> (raw)
In-Reply-To: <00000140bb35f38a-99d5d8ab-6672-42e8-9e91-55cb231c693d-000000@email.amazonses.com>
On Mon, 26 Aug 2013 15:20:09 +0000
Christoph Lameter <cl@linux.com> wrote:
> On Mon, 26 Aug 2013, Steven Rostedt wrote:
>
> > As Tejun said, each commit needs its own change log. Never expect a
> > change lgo from another commit to be read for changes in this commit.
>
> I can copy the intro into each of the patches?
That probably would be fine.
> >
> > This patch needs to be broken up per subsystem. Or are you just looking
> > for acks from all the maintainers here and you'll pull it in. If that's
> > the case, you should have Cc'd each of the maintainers of the files that
> > this touches.
>
> I did a breakout by arch, then core and drivers. How fine grained do you
> want them? This touches a significant portion of the kernel source.
> There could be quite a number of maintainers involved.
If you plan on sending the patch, then just get an ack for each of the
maintainers that this code touches. At least Cc them. Yeah, there are a
significant number of maintainers but not that many that it will cause
the email to be bounced from LKML for too many Cc's.
An Acked-by from David Miller will cover all of net/ subsystem. Maybe
make that a separate patch?
I can do the tracing patches.
Thomas Gleixner can ack all the timing changes.
Peter Zijlstra and Ingo Molnar can do the rest of the kernel/ changes.
I assume that Andrew Morton can take care of the mm/ changes and
perhaps even the radix tree changes.
-- Steve
next prev parent reply other threads:[~2013-08-26 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130823190135.726207430@linux.com>
2013-08-23 19:01 ` [guv 01/16] x86: Use this_cpu_inc/dec for debug registers Christoph Lameter
2013-08-23 19:01 ` [guv 02/16] percpu: Make __verify_pcu_ptr handle per cpu pointers to arrays Christoph Lameter
2013-08-23 20:09 ` Tejun Heo
2013-08-23 19:02 ` [guv 11/16] powerpc: __get_cpu_var conversion Christoph Lameter
2013-08-23 19:02 ` [guv 12/16] sparc: " Christoph Lameter
2013-08-27 20:04 ` David Miller
2013-08-23 19:02 ` [guv 05/16] drivers: Convert __get_cpu_var uses Christoph Lameter
2013-08-23 19:02 ` [guv 04/16] core: " Christoph Lameter
2013-08-26 14:18 ` Steven Rostedt
2013-08-26 15:20 ` Christoph Lameter
2013-08-26 15:31 ` Steven Rostedt [this message]
2013-08-23 19:02 ` [guv 03/16] Coccinelle script for __get_cpu_var conversion Christoph Lameter
2013-08-23 19:02 ` [guv 15/16] misc arches " Christoph Lameter
2013-08-23 19:02 ` [guv 16/16] Remove __get_cpu_var and __raw_get_cpu_var macros Christoph Lameter
2013-08-23 19:02 ` [guv 09/16] s390: __get_cpu_var conversion Christoph Lameter
2013-08-23 19:02 ` [guv 08/16] mips: " Christoph Lameter
2013-08-23 19:02 ` [guv 14/16] tile: " Christoph Lameter
2013-08-23 19:02 ` [guv 07/16] x86: Convert __get_cpu_var uses Christoph Lameter
2013-08-23 19:02 ` [guv 13/16] arm: __get_cpu_var conversion Christoph Lameter
2013-08-23 19:02 ` [guv 06/16] staging: Convert __get_cpu_var uses Christoph Lameter
2013-08-23 19:02 ` [guv 10/16] ia64: __get_cpu_var conversion Christoph Lameter
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=20130826113134.5306379d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®