From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Tony Lindgren <tony@atomide.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [alsa-devel] [RFC][PATCH 1/3 v2] ARM: OMAP: DMA: Add support for DMA channel self linking on OMAP1510
Date: Sun, 23 Aug 2009 18:03:59 +0100 [thread overview]
Message-ID: <20090823170359.GA3488@sirena.org.uk> (raw)
In-Reply-To: <200908231756.13016.jkrzyszt@tis.icnet.pl>
On Sun, Aug 23, 2009 at 05:56:12PM +0200, Janusz Krzysztofik wrote:
> I know it's not very fair to change the patch after others that depend on it
> have already been applied, but I hope there will be no problems with accepting
> the way I have reimplemented it. In any case, I'll appreciate any comments or
> suggestions.
It's not that it's not fair, at this point it's not possible - please
make any changes you feel are required against current ASoC. The patch
has been applied for a little while now and is buried quite deep in the
already published history.
next prev parent reply other threads:[~2009-08-23 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:50 [RFC][PATCH 1/3] ARM: OMAP: DMA: Add support for DMA channel self linking on OMAP1510 Janusz Krzysztofik
2009-08-17 9:16 ` Jarkko Nikula
2009-08-23 15:56 ` [RFC][PATCH 1/3 v2] " Janusz Krzysztofik
2009-08-23 17:03 ` Mark Brown [this message]
2009-08-23 17:45 ` [alsa-devel] " Janusz Krzysztofik
2009-08-23 18:05 ` Mark Brown
2009-08-23 18:38 ` Janusz Krzysztofik
2009-08-23 18:49 ` Mark Brown
2009-08-24 5:49 ` Jarkko Nikula
2009-08-24 12:49 ` Tony Lindgren
2009-08-24 22:06 ` 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=20090823170359.GA3488@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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