From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Russell King <rmk+alsa@arm.linux.org.uk>
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 10:46:41 +0100 [thread overview]
Message-ID: <20110915094640.GA7988@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110914233838.GB22946@flint.arm.linux.org.uk>
On Thu, Sep 15, 2011 at 12:38:39AM +0100, Russell King wrote:
> On Thu, Sep 15, 2011 at 12:28:09AM +0100, Mark Brown wrote:
> > On Wed, Sep 14, 2011 at 08:19:17PM +0100, Russell King wrote:
> > ...this is true a substantial proportion of the GTA01 devices out there
> > are in the hands of people who might hack on it.
> Point at a mainline kernel which includes support for the neo1973_gta01
> platform.
I don't recall saying that there has been one; however I have seen
reasonable (if sporadic) efforts at getting the two boards mainlined -
it took years to get GTA02 in there but it did happen.
next prev parent reply other threads:[~2011-09-15 9:46 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 [this message]
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
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=20110915094640.GA7988@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=laforge@openezx.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rmk+alsa@arm.linux.org.uk \
/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.