From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Tony Lindgren <tony@atomide.com>,
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.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [PATCH 3/3 v3] ASoC: OMAP: Enhance OMAP1510 DMA progress software counter
Date: Tue, 18 Aug 2009 19:57:01 +0300 [thread overview]
Message-ID: <20090818195701.6f260d33.jhnikula@gmail.com> (raw)
In-Reply-To: <20090818134540.GB24620@sirena.org.uk>
On Tue, 18 Aug 2009 14:45:41 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, Aug 18, 2009 at 03:42:05PM +0200, Janusz Krzysztofik wrote:
>
> > And now, how is the patch 1/3 supposed to get into the mainline? Whom
> > should I ping from time to time to get it integrated? If not then, as
> > you know for sure, applying patch 2/3 whithout 1/3 will result in ASoC
> > support for OMAP1510 broken.
>
> Normally the OMAP tree, though that's possibly a bit tricky due to the
> ARM tree closing early. If Tony's OK with merging via the ALSA tree we
> could also apply the ARM patch there?
I would say that it's better to keep in Tony's hand since otherwise
there can be risk for DMA code being out-of-sync as there are quite
frequent other PM, OMAP4, errata, etc. patches coming into it.
Of course it means that OMAP1510 audio is broken until the patch 1/3 is
merged but probably patch can be merged as a fix if merge window is
missed.
--
Jarkko
next prev parent reply other threads:[~2009-08-18 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:50 [RFC] [PATCH 3/3] ASoC: OMAP: Enhance OMAP1510 DMA progress software counter Janusz Krzysztofik
2009-08-10 9:43 ` Janusz Krzysztofik
2009-08-10 21:11 ` Janusz Krzysztofik
2009-08-10 23:07 ` [RFC][PATCH 3/3 v2] " Janusz Krzysztofik
2009-08-11 6:42 ` Jarkko Nikula
2009-08-11 9:30 ` Janusz Krzysztofik
2009-08-11 19:44 ` [PATCH 3/3 v3] " Janusz Krzysztofik
2009-08-17 9:26 ` Jarkko Nikula
2009-08-17 10:03 ` Mark Brown
2009-08-18 13:42 ` Janusz Krzysztofik
2009-08-18 13:45 ` Mark Brown
2009-08-18 16:57 ` Jarkko Nikula [this message]
2009-08-24 12:50 ` Tony Lindgren
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=20090818195701.6f260d33.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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