public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: tim.gardner@canonical.com,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: 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 10:54:59 -0800	[thread overview]
Message-ID: <20120203185459.GA7321@kroah.com> (raw)
In-Reply-To: <20120203185319.GA1710@kroah.com>

On Fri, Feb 03, 2012 at 10:53:19AM -0800, Greg KH wrote:
> On Fri, Feb 03, 2012 at 10:51:57AM -0800, Greg KH wrote:
> > On Fri, Feb 03, 2012 at 11:41:04AM -0700, Tim Gardner wrote:
> > > On 02/03/2012 10:47 AM, Greg KH wrote:
> > > >I'm announcing the release of the 3.2.3 kernel.
> > > >
> > > >All users of the 3.2 kernel series must upgrade.
> > > >
> > > >The updated 3.2.y git tree can be found at:
> > > >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.2.y
> > > >and can be browsed at the normal kernel.org git web browser:
> > > >         http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > > >
> > > >thanks,
> > > >
> > > >greg k-h
> > > >
> > > 
> > > Build failure in vanilla Linux 3.2.3:
> > > 
> > >   CC [M]  sound/soc/codecs/wm5100.o
> > > sound/soc/codecs/wm5100.c: In function ‘wm5100_set_bias_level’:
> > > sound/soc/codecs/wm5100.c:1382:33: error: ‘struct wm5100_priv’ has
> > > no member named ‘regmap’
> > > sound/soc/codecs/wm5100.c:1398:33: error: ‘struct wm5100_priv’ has
> > > no member named ‘regmap’
> > > sound/soc/codecs/wm5100.c:1409:29: error: ‘struct wm5100_priv’ has
> > > no member named ‘regmap’
> > > make[5]: *** [sound/soc/codecs/wm5100.o] Error 1
> > > 
> > > Looks like it depends on bd132ec585c498ee27d7eedf8569703606743928
> > > "ASoC: Convert wm5100 to direct regmap API usage", but I haven't
> > > re-built with it yet.
> > > 
> > > See attached config.
> > 
> > Ugh, I didn't have CONFIG_SND_SOC=m in my test config files, I'll go fix
> > that now and see what needs to be done here, thanks for letting me know.
> > 
> > Mark any hints?
> 
> 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:
 sound/soc/codecs/wm5100-tables.c | 1488 +++++++++++++++++++--------------------
 sound/soc/codecs/wm5100.c        |   51 +
 sound/soc/codecs/wm5100.h        |    7 
 3 files changed, 787 insertions(+), 759 deletions(-)

Which is a bit big.

Mark, any objection to me just reverting the SOC patch that causes this build
failure instead?

thanks,

greg k-h

  reply	other threads:[~2012-02-03 18:55 UTC|newest]

Thread overview: 12+ 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:51   ` Greg KH
2012-02-03 18:53     ` Greg KH
2012-02-03 18:54       ` Greg KH [this message]
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
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=20120203185459.GA7321@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox