From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: tim.gardner@canonical.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: Linux 3.2.3
Date: Fri, 3 Feb 2012 12:34:46 -0800 [thread overview]
Message-ID: <20120203203446.GA15738@kroah.com> (raw)
In-Reply-To: <20120203192216.GA12724@kroah.com>
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
next prev parent reply other threads:[~2012-02-03 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 17:47 Linux 3.2.3 Greg KH
2012-02-03 17:48 ` Greg KH
2012-02-03 18:41 ` Tim Gardner
2012-02-03 18:41 ` Tim Gardner
2012-02-03 18:51 ` Greg KH
2012-02-03 18:53 ` Greg KH
2012-02-03 18:54 ` Greg KH
2012-02-03 19:11 ` Tim Gardner
2012-02-03 19:27 ` Mark Brown
2012-02-03 19:14 ` Mark Brown
2012-02-03 19:22 ` Greg KH
2012-02-03 20:34 ` Greg KH [this message]
2012-02-03 20:30 ` Greg KH
2012-02-03 20:30 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120203203446.GA15738@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tim.gardner@canonical.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.