From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: Liam Girdwood <lrg-l0cyMroinI0@public.gmane.org>,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH V2 2/4] ASoC: convert Tegra20 I2S driver to regmap
Date: Fri, 13 Apr 2012 12:13:23 -0600 [thread overview]
Message-ID: <4F886CC3.90302@wwwdotorg.org> (raw)
In-Reply-To: <20120413173012.GZ3168-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
On 04/13/2012 11:30 AM, Mark Brown wrote:
> On Fri, Apr 13, 2012 at 11:23:37AM -0600, Stephen Warren wrote:
>> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> Signed-off-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> ---
>> v2: Split into separate patch
>
> Can you regenerate these against for-3.5 please?
Oh right, "ASoC: tegra: ensure clocks are enabled when touching
registers" is only in for-3.4 not for-3.5. Will regenerate. Sorry about
that.
BTW, when merging your for-3.4 into for-3.5, or when rebasing your
for-3.5 onto a new v3.4-rcN, you'll want to just ignore the change from
the patch I mentioned above since it touches code deleted in for-3.5
once these patches are applied.
next prev parent reply other threads:[~2012-04-13 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 17:23 [PATCH V2 1/4] ASoC: tegra: select REGMAP_MMIO Stephen Warren
2012-04-13 17:23 ` [PATCH V2 2/4] ASoC: convert Tegra20 I2S driver to regmap Stephen Warren
2012-04-13 17:30 ` Mark Brown
[not found] ` <20120413173012.GZ3168-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-04-13 18:13 ` Stephen Warren [this message]
2012-04-13 17:23 ` [PATCH V2 3/4] ASoC: convert Tegra20 SPDIF " Stephen Warren
2012-04-13 17:23 ` [PATCH V2 4/4] ASoC: convert Tegra20 DAS " Stephen Warren
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=4F886CC3.90302@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).