mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: akpm@linuxfoundation.org, linux-arch@vger.kernel.org,
	Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [guv 00/16] [RFC] percpu: Replace __get_cpu_var uses throughout the kernel
Date: Mon, 26 Aug 2013 14:18:00 -0400	[thread overview]
Message-ID: <20130826181800.GA25997@mtj.dyndns.org> (raw)
In-Reply-To: <00000140bb37931e-fbfdfad2-8241-40cc-b053-7c53d54a9728-000000@email.amazonses.com>

Hey, Christoph.

On Mon, Aug 26, 2013 at 03:21:56PM +0000, Christoph Lameter wrote:
> On Fri, 23 Aug 2013, Tejun Heo wrote:
> 
> > * It would be a lot easier to route the patches if each had cc's to
> >   the maintainers of the affected subsystems.
> 
> So the drivers patch needs to CC all driver maintainers?

There usually is a maintainer for a whole lot of similar drivers - one
for infiniband, one for v4l and so on, so the list usually isn't that
long.

> There must be some easier way to get this done.

It can be consolidated and pushed as a single series either through
the percpu tree or -mm but it still at least needs to inform the
people working on the affected code and get the confirmations where
possible.

> Not sure how to do this. Thats why its an RFC. I cced Andrew because he
> usually knows how to deal with massive patches like this.

It can go two ways.

* Split further so that the patches can be merged through separate
  branches so that they converge on the next merge window where the
  leftovers can be taken care of and further dependent changes merged.

* Get acks from most maintainers and push the changes as a single
  series through either percpu tree or -mm.  The benefits of going
  through -mm is that -mm floats on top of all changes scheduled for
  the next merge window, so if the changes in question are likely to
  conflict with other changes in various subsystems scheduled for the
  next merge window, -mm is easier.  Given the nature of the changes,
  I don't think going through percpu or -mm would make much
  difference.

Thanks.

-- 
tejun

  reply	other threads:[~2013-08-26 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 19:01 Christoph Lameter
2013-08-23 20:05 ` Tejun Heo
2013-08-26 15:21   ` Christoph Lameter
2013-08-26 18:18     ` Tejun Heo [this message]
2013-08-27  4:57 ` Stephen Rothwell
2013-08-27 15:39   ` 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=20130826181800.GA25997@mtj.dyndns.org \
    --to=tj@kernel.org \
    --cc=akpm@linuxfoundation.org \
    --cc=cl@linux.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.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

all inboxes | Powered by JetHome®