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] [thread-next>] [day] [month] [year] [list]

Message-ID: <00000140bb35f38a-99d5d8ab-6672-42e8-9e91-55cb231c693d-000000@email.amazonses.com>
Date:	Mon, 26 Aug 2013 15:20:09 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Steven Rostedt <rostedt@...dmis.org>
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, 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?

> > Index: linux/kernel/time/tick-oneshot.c
> > Index: linux/kernel/trace/ftrace.c
> > Index: linux/kernel/user-return-notifier.c
> > Index: linux/kernel/watchdog.c
> > Index: linux/lib/radix-tree.c
> > Index: linux/mm/memcontrol.c
> > Index: linux/mm/memory-failure.c
> > Index: linux/mm/page-writeback.c
> > Index: linux/mm/swap.c
> > Index: linux/mm/vmalloc.c
> > Index: linux/mm/vmstat.c
> > Index: linux/net/core/dev.c
> > Index: linux/net/core/drop_monitor.c
> > Index: linux/net/core/skbuff.c
> > Index: linux/net/ipv4/tcp_output.c
> > Index: linux/net/rds/ib_rdma.c
> > Index: linux/kernel/timer.c
> > Index: linux/kernel/trace/trace.c
>
> 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.


--
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/