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:	Fri, 14 Sep 2012 09:07:23 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Fengguang Wu <fengguang.wu@...el.com>,
	Amit Daniel Kachhap <amit.kachhap@...aro.org>,
	Zhang Rui <rui.zhang@...el.com>
Subject: Re: linux-next: build failure after merge of the akpm tree

Hi Andrew,

On Thu, 13 Sep 2012 18:31:06 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Here is the chunk of the series file I have:
> 
> idr-rename-max_level-to-max_idr_level.patch
> idr-rename-max_level-to-max_idr_level-fix.patch
> idr-rename-max_level-to-max_idr_level-fix-fix-2.patch
> #NEXT_PATCHES_END
> #
> linux-next.patch
> i-need-old-gcc.patch
> idr-rename-max_level-to-max_idr_level-fix-3.patch
> arch-alpha-kernel-systblss-remove-debug-check.patch
> #
> #NEXT_PATCHES_START linux-next-urgent
> 
> So idr-rename-max_level-to-max_idr_level-fix-3.patch is excluded form
> linux-next :-( I guess I need to just move that further down in the
> series file?  Though when you send the preceding three patches to Linus,
> that fix-3 patch will be needed when I merge the thermal tree.

I put idr-rename-max_level-to-max_idr_level-fix-3.patch into the akpm
tree in linux-next (just after the -fix-2 patch).

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

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ