linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] sound: tegra_wm8903: Adjust to of_get_named_gpio() change
Date: Mon, 18 Jun 2012 19:15:46 +0200	[thread overview]
Message-ID: <4FDF6242.3040400@antcom.de> (raw)
In-Reply-To: <20120618170408.GW3974@opensource.wolfsonmicro.com>

On 06/18/2012 07:04 PM, Mark Brown wrote:
> On Mon, Jun 18, 2012 at 07:00:14PM +0200, Roland Stigge wrote:
> 
>> Basically, yes. But this would mean that doing via gpio, we would
>> need to pull other stuff from the sound tree over to gpio to
>> build upon because "my" tegra_* sound patches won't apply to the
>> gpio branch currently.
> 
> Oh, yes.  Stephen's gone and reorganised all that code which means
> it's not a trivial merge.  Ho hum.  I'm happy to apply them if
> folks are comfortable with it, I guess ideally I'd be able to pull
> a branch with the gpio changes in and then apply on top of that.

Depending on what else changes will come via gpio for 3.6, maybe you
don't even need to merge gpio to sound?

Can you please coordinate between sound and gpio?

Thanks in advance!

Roland

PS: I'm posting a combined patch suitable for the sound subsystem.
Please tell me if you also need the gpiolib-of patch singled out.

  reply	other threads:[~2012-06-18 17:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 16:42 [PATCH 1/2] sound: tegra_wm8903: Adjust to of_get_named_gpio() change Roland Stigge
2012-06-18 16:42 ` [PATCH 2/2] sound: tegra_alc5632: " Roland Stigge
2012-06-18 17:28   ` Alexandre Pereira da Silva
2012-06-19  6:29     ` Leon Romanovsky
2012-06-19 10:03       ` Alexandre Pereira da Silva
2012-06-19 11:03         ` Roland Stigge
2012-06-18 16:46 ` [PATCH 1/2] sound: tegra_wm8903: " Mark Brown
2012-06-18 17:00   ` Roland Stigge
2012-06-18 17:04     ` Mark Brown
2012-06-18 17:15       ` Roland Stigge [this message]
2012-06-18 17:28 ` Alexandre Pereira da Silva
2012-07-26 21:25 ` 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=4FDF6242.3040400@antcom.de \
    --to=stigge@antcom.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).