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>,
Laxman Dewangan
<ldewangan-DDmLM1+adcrQT0dZR+AlfA@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] ASoC: tegra: fix maxburst settings in dmaengine code
Date: Thu, 06 Sep 2012 19:36:12 -0600 [thread overview]
Message-ID: <50494F8C.3030906@wwwdotorg.org> (raw)
In-Reply-To: <20120907010050.GE4400-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
On 09/06/2012 07:00 PM, Mark Brown wrote:
> On Thu, Sep 06, 2012 at 05:47:33PM -0600, Stephen Warren wrote:
>
>> Mark, I'd like to take this patch through the Tegra tree, since it's a
>> dependency for the series that converts Tegra to dmaengine. Thanks.
>
> Since it's a fix I was going to send it as a patch for 3.6 so that
> shouldn't be an issue?
Oh right, that makes sense too, thanks.
next prev parent reply other threads:[~2012-09-07 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 23:47 [PATCH] ASoC: tegra: fix maxburst settings in dmaengine code Stephen Warren
[not found] ` <1346975253-2935-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-07 1:00 ` Mark Brown
[not found] ` <20120907010050.GE4400-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-09-07 1:36 ` Stephen Warren [this message]
[not found] ` <50494F8C.3030906-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-10 18:03 ` Stephen Warren
[not found] ` <504E2B73.2020006-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-11 0:05 ` Mark Brown
2012-09-07 1:51 ` 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=50494F8C.3030906@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=ldewangan-DDmLM1+adcrQT0dZR+AlfA@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).