linux-kernel - Re: [PATCH 4.5 000/238] 4.5.1-stable review

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: <20160412143230.GB10285@kroah.com>
Date:	Tue, 12 Apr 2016 07:32:30 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, shuah.kh@...sung.com,
	patches@...nelci.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.5 000/238] 4.5.1-stable review

On Sun, Apr 10, 2016 at 11:43:47PM -0700, Guenter Roeck wrote:
> On 04/10/2016 11:32 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.5.1 release.
> > There are 238 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Tue Apr 12 18:34:18 UTC 2016.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
> 	total: 147 pass: 147 fail: 0
> Qemu test results:
> 	total: 104 pass: 100 fail: 4
> Failed tests:
> 	arm:akita:pxa_defconfig
> 	arm:borzoi:pxa_defconfig
> 	arm:spitz:pxa_defconfig
> 	arm:terrier:pxa_defconfig
> 
> Details are available at http://kerneltests.org/builders.
> 
> 4.5 will require two patches from mainline to fix the known problems.
> 
> 3c2e2266a5bd ("hwmon: (max1111) Return -ENODEV from max1111_read_channel if not instantiated")
> c4e5ffb6f224 ("gpio: pxa: fix legacy non pinctrl aware builds")
> 
> The first fixes the direct failures reported above, the second fixes
> a traceback seen as result of failed gpio pin initialization. The
> first patch is tagged Cc: stable, the second has a Fixes: tag,
> so both should already be in your queue for 4.5.

Yes, both should be queued up for the next round of 4.5-stable patches,
I'll let them get merged then.

Thanks for testing and letting me know.

greg k-h