From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Roland Stigge <stigge@antcom.de>
Cc: swarren@wwwdotorg.org, cjb@laptop.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rmk+kernel@arm.linux.org.uk,
ulf.hansson@stericsson.com, linus.walleij@linaro.org,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
aletes.xgr@gmail.com, linux-arm-kernel@lists.infradead.org,
lrg@ti.com, perex@perex.cz, tiwai@suse.de,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] sound: tegra_wm8903: Adjust to of_get_named_gpio() change
Date: Mon, 18 Jun 2012 18:04:08 +0100 [thread overview]
Message-ID: <20120618170408.GW3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FDF5E9E.6060803@antcom.de>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
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 18:04:08 +0100 [thread overview]
Message-ID: <20120618170408.GW3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FDF5E9E.6060803@antcom.de>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120618/135b3d89/attachment.sig>
next prev parent reply other threads:[~2012-06-18 17:04 UTC|newest]
Thread overview: 24+ 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 ` Roland Stigge
2012-06-18 16:42 ` [PATCH 2/2] sound: tegra_alc5632: " Roland Stigge
2012-06-18 16:42 ` Roland Stigge
2012-06-18 17:28 ` Alexandre Pereira da Silva
2012-06-18 17:28 ` Alexandre Pereira da Silva
2012-06-19 6:29 ` Leon Romanovsky
2012-06-19 6:29 ` Leon Romanovsky
2012-06-19 10:03 ` Alexandre Pereira da Silva
2012-06-19 10:03 ` Alexandre Pereira da Silva
2012-06-19 11:03 ` Roland Stigge
2012-06-19 11:03 ` Roland Stigge
2012-06-18 16:46 ` [PATCH 1/2] sound: tegra_wm8903: " Mark Brown
2012-06-18 16:46 ` Mark Brown
2012-06-18 17:00 ` Roland Stigge
2012-06-18 17:00 ` Roland Stigge
2012-06-18 17:04 ` Mark Brown [this message]
2012-06-18 17:04 ` Mark Brown
2012-06-18 17:15 ` Roland Stigge
2012-06-18 17:15 ` Roland Stigge
2012-06-18 17:28 ` Alexandre Pereira da Silva
2012-06-18 17:28 ` Alexandre Pereira da Silva
2012-07-26 21:25 ` Mark Brown
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=20120618170408.GW3974@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=aletes.xgr@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=stigge@antcom.de \
--cc=swarren@wwwdotorg.org \
--cc=tiwai@suse.de \
--cc=ulf.hansson@stericsson.com \
/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.