linux-kernel - Re: [guv 00/16] [RFC] percpu: Replace __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: <00000140bb37931e-fbfdfad2-8241-40cc-b053-7c53d54a9728-000000@email.amazonses.com>
Date:	Mon, 26 Aug 2013 15:21:56 +0000
From:	Christoph Lameter <cl@...ux.com>
To:	Tejun Heo <tj@...nel.org>
cc:	akpm@...uxfoundation.org, linux-arch@...r.kernel.org,
	Steven Rostedt <srostedt@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [guv 00/16] [RFC] percpu: Replace __get_cpu_var uses throughout
 the kernel

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 must be some easier way to get this done.

> * Dunno what's the convention around conccinelle scripts but do we
>   need to keep them around if the accessor being converted gets
>   removed at the end of the series?
>
> How do you want to route the patches?  I'm gonna apply the second
> patch which updates __verify_pcpu_ptr() to the percpu tree right away
> and push it to Linus early during the merge window so that pushing
> other patches through different trees from there on isn't too painful.

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.

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