[alsa-devel] [PATCH v3 3/4] ARM: tegra: Platform data fixes for ASoC driver updates

Stephen Warren swarren at nvidia.com
Fri Jan 21 19:22:11 CET 2011

Mark Brown wrote:
> It'd also be helpful if you could stop burying patches in old threads -
> it makes it hard to find the most recent stuff.

Sorry. I read somewhere that threading updates into the existing thread was the 
preferred way. I'll stop doing it.

> > To be explicit, the only dependency is that the patch quoted above, which
> > adds some platform data types, needs to be checked in to te ASoC tree
> > rather than the usual ARM tree, before the following ASoC patch is
> > applied:
> ...but possibly not?

Sorry, I don't follow. Possibly not what? Are you saying:

a) Possibly not the only dependency? It's certainly the only one I know of.

b) Possibly not that it needs to be checked into the ASoC git repo, even though
the header is located somewhere the Tegra git repo owns?

I'm fine moving the header into some directory that ASoC owns, and fixing my
arch/arm/mach-tegra patch for the new location. That would mean that when I
submit the Tegra changes to the Tegra tree, the Tegra trees needs to have picked
up the ASoC changes first, but that's fine I think? At the least, it defers any issue
until later.

Otherwise, yes, that patch is needed befoer the ASoC patch that uses it, or there
will be a build break, if anyone enables building that driver.


More information about the Alsa-devel mailing list