From: Roland Stigge <stigge@antcom.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 19:00:14 +0200 [thread overview]
Message-ID: <4FDF5E9E.6060803@antcom.de> (raw)
In-Reply-To: <20120618164659.GV3974@opensource.wolfsonmicro.com>
On 06/18/2012 06:46 PM, Mark Brown wrote:
> On Mon, Jun 18, 2012 at 06:42:21PM +0200, Roland Stigge wrote:
>> of_get_named_gpio() was changed to return -EPROBE_DEFER in case of
>> gpios not probed yet. This patch adjusts tegra_wm8903 to this.
>
> So, I saw from the other thread that this didn't actually happen yet - I
> guess the best thing is to merge this along with the changes for
> introducing -EPROBE_DEFER.
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.
Any hint welcome.
Thanks in advance,
Roland
next prev parent reply other threads:[~2012-06-18 17:00 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 [this message]
2012-06-18 17:04 ` Mark Brown
2012-06-18 17:15 ` Roland Stigge
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=4FDF5E9E.6060803@antcom.de \
--to=stigge@antcom.de \
--cc=aletes.xgr@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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=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 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).