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]
Date:	Thu, 7 Jul 2016 12:15:25 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Kevin Hilman <khilman@...libre.com>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux@...ck-us.net,
	shuah.kh@...sung.com, patches@...nelci.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/32] 4.4.15-stable review

On Thu, Jul 07, 2016 at 09:53:10AM -0700, Kevin Hilman wrote:
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
> 
> > This is the start of the stable review cycle for the 4.4.15 release.
> > There are 32 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.
> 
> We were looking into why the kernelci.org bot isn't responding to this
> and it's because the actual patch count in the git tree is 33 (not 32)
> because it includes the commit adds -rc1 to the Makefile.  So, the
> kernelci bot was waiting for a build to show up that matched this email
> (which it didn't find.)
> 
> Can you update your scripts to include that final patch so the patch
> count is right?  It's already included in the one-big patch, and the
> diffstat etc. below, so that would make everything line up.
> 
> > Responses should be made by Sat Jul  9 01:16:17 UTC 2016.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > 	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.15-rc1.gz
> 
> nit: this isn't a working URL, and adding an https://www.  prefix onto that,
> that file dosen't seem to exist there yet.

Should be there soon, sorry, an error on my end.

I'll look into fixing all these things when I return from LinuxCon
Japan, right now I'm on vacation and really don't want to be messing
with my stable scripts...

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ