linux-kernel - Re: [GIT PULL] Phase 2 of _

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]

Date:	Thu, 18 Jul 2013 15:24:04 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Phase 2 of __cpuinit removal

Hi Linus,

On Mon, 15 Jul 2013 10:57:35 -0400 Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
>
> Please pull the following to get phase two of the __cpuinit removal.
> 
> With the __cpuinit infrastructure removed earlier, this group of commits
> only removes the function/data tagging that was done with the various
> (now no-op) __cpuinit related prefixes.
> 
> Now that the dust has settled with yesterday's v3.11-rc1, there hopefully
> shouldn't be any new users leaking back in tree, but I think we can leave
> the harmless no-op stubs there for a release as a courtesy to those who
> still have out of tree stuff and weren't paying attention.
> 
> Although the commits are against the recent tag to allow for minor context
> refreshes for things like yesterday's v3.11-rc1~ slab content, the patches
> have been largely unchanged for weeks, aside from such trivial updates. 
> 
> For detail junkies, the largely boring and mostly irrelevant history of
> the patches can be viewed at:
> 
>  http://git.kernel.org/cgit/linux/kernel/git/paulg/cpuinit-delete.git
> 
> If nothing else, I guess it does at least demonstrate the level of
> involvement required to shepherd such a treewide change to completion.
> 
> This is the same repository of patches that has been applied to the
> end of the daily linux-next branches for the past several weeks.
> 
> The branch below represents a direct "git am" of the above patch repo
> (that is similarly tagged with v3.11-rc1) to mainline's v3.11-rc1.

It would be good if this could go in soon as I am already seeing (so far
trivial) conflicts against some of these.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped