[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090818195701.6f260d33.jhnikula@gmail.com>
Date: Tue, 18 Aug 2009 19:57:01 +0300
From: Jarkko Nikula <jhnikula@...il.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Janusz Krzysztofik <jkrzyszt@....icnet.pl>,
Peter Ujfalusi <peter.ujfalusi@...ia.com>,
Tony Lindgren <tony@...mide.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.arm.linux.org.uk"
<linux-arm-kernel@...ts.arm.linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3 v3] ASoC: OMAP: Enhance OMAP1510 DMA progress
software counter
On Tue, 18 Aug 2009 14:45:41 +0100
Mark Brown <broonie@...nsource.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists