All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jaroslav Kysela <perex@perex.cz>,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Zeng Zhaoming <b32542@freescale.com>
Subject: Re: [build failure] Re: [GIT PULL] sound updates for 2.6.39-rc1
Date: Tue, 22 Mar 2011 12:24:36 +0000	[thread overview]
Message-ID: <20110322122436.GA6834@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110321165827.GG2570@opensource.wolfsonmicro.com>

On Mon, Mar 21, 2011 at 04:58:27PM +0000, Mark Brown wrote:
> That's the breakage, yes.  It should be very straightforward to make the
> driver build no matter how CONFIG_REGULATOR is set.

And indeed it was - in the absence of any response from Zeng I've now
sent a patch for review.

  reply	other threads:[~2011-03-22 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 14:05 [GIT PULL] sound updates for 2.6.39-rc1 Takashi Iwai
2011-03-21 15:37 ` [build failure] " Ingo Molnar
2011-03-21 15:42   ` Randy Dunlap
2011-03-21 15:56   ` Takashi Iwai
2011-03-21 15:58   ` Mark Brown
2011-03-21 16:11     ` Ingo Molnar
2011-03-21 16:38       ` Mark Brown
2011-03-21 16:49         ` Ingo Molnar
2011-03-21 16:58           ` Mark Brown
2011-03-22 12:24             ` Mark Brown [this message]
2011-03-22 15:38               ` Randy Dunlap
2011-03-22 15:50                 ` Mark Brown
2011-03-22 15:51                 ` Takashi Iwai
2011-03-22 15:57                   ` Randy Dunlap
2011-03-22 16:00                   ` Ingo Molnar
2011-03-22 16:41                     ` Mark Brown

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=20110322122436.GA6834@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=b32542@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=mingo@elte.hu \
    --cc=perex@perex.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=tiwai@suse.de \
    --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.