From: Russell King <rmk+alsa@arm.linux.org.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Axel Lin <axel.lin@gmail.com>, Harald Welte <laforge@openezx.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lrg@ti.com>, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [linux-next] ASoC: sound/soc/samsung/neo1973_wm8753.c build failure
Date: Thu, 15 Sep 2011 20:16:30 +0100 [thread overview]
Message-ID: <20110915191630.GA21615@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20110915133122.GG7988@opensource.wolfsonmicro.com>
On Thu, Sep 15, 2011 at 02:31:22PM +0100, Mark Brown wrote:
> On Thu, Sep 15, 2011 at 12:00:56PM +0100, Russell King wrote:
> > If it's not dead then it needs sorting out. Either way there's two
> > valid states: 1. fully merged, or 2. none of it is merged.
> > There's no real half-way house state - certainly not one which should
> > persist for three years. (It would be reasonable for maybe a couple
> > of kernel releases but more than that is becoming very much a joke.)
>
> I'm not really aware of what's going on with the arch/arm code but from
> an ASoC point of view it's one of the platforms people seem to usefully
> care about; there's more traffic than for most machines. Obviously the
> problems with s3c24xx aren't going to have been helpful either.
It sounds like you're in the perfect place to send them a warning
that something needs to happen on this, one way or the other.
Whether anyone volunteers should be used as a factor in deciding
how to deal with the small bits of GTA01 support in mainline.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-09-15 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 9:18 [linux-next] ASoC: sound/soc/samsung/neo1973_wm8753.c build failure Axel Lin
2011-09-14 19:19 ` Russell King
2011-09-14 23:28 ` Mark Brown
2011-09-14 23:28 ` Mark Brown
2011-09-14 23:38 ` Russell King
2011-09-15 9:46 ` Mark Brown
2011-09-15 11:00 ` Russell King
2011-09-15 11:53 ` Lars-Peter Clausen
2011-09-15 11:53 ` Lars-Peter Clausen
2011-09-15 12:06 ` Russell King
2011-09-16 17:02 ` Valdis.Kletnieks
2011-09-16 17:02 ` Valdis.Kletnieks
2011-09-16 20:03 ` Russell King
2011-09-15 13:31 ` Mark Brown
2011-09-15 13:31 ` Mark Brown
2011-09-15 19:16 ` Russell King [this message]
2011-09-15 22:39 ` Mark Brown
2011-09-15 22:39 ` Mark Brown
2011-09-15 7:20 ` Harald Welte
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=20110915191630.GA21615@flint.arm.linux.org.uk \
--to=rmk+alsa@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=laforge@openezx.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.