linux-kernel - Re: [guv 04/16] core: Convert __get_cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130826113134.5306379d@gandalf.local.home>
Date:	Mon, 26 Aug 2013 11:31:34 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [guv 04/16] core: Convert __get_cpu_var uses

On Mon, 26 Aug 2013 15:20:09 +0000
Christoph Lameter <cl@...ux.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/