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]
Message-ID: <20120203203446.GA15738@kroah.com>
Date:	Fri, 3 Feb 2012 12:34:46 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	tim.gardner@...onical.com, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org
Subject: Re: Linux 3.2.3

On Fri, Feb 03, 2012 at 11:22:16AM -0800, Greg KH wrote:
> On Fri, Feb 03, 2012 at 07:14:39PM +0000, Mark Brown wrote:
> > On Fri, Feb 03, 2012 at 10:54:59AM -0800, Greg KH wrote:
> > > On Fri, Feb 03, 2012 at 10:53:19AM -0800, Greg KH wrote:
> > 
> > > > Yes, the above commit fixes the build for me, thanks, I'll go release
> > > > 3.2.4 with this build fix in it, thanks Tim for letting me know.
> > 
> > > Hm, no, I don't think I'll really trust that patch for a -stable
> > > release, it looks like:
> > 
> > That's not -stable material at all.  The functions concerned will need
> > to be replaced with their snd_soc equivalents:
> > 
> > 	regache_cache_bypass -> assign to codec->cache_bypass
> > 	regcache_cache_only -> assign to codec->cache_only
> > 
> > It may be Monday before I can cook up a patch.
> 
> How about I just revert the 2 patches Tim pointed out, which will get
> 3.2.3 building properly, and then you can resend them when you get them
> reworked sometime in the future?

This seems the simplest, I've now done this and will release 3.2.4 in a
short while.

greg k-h
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ