From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Sangbeom Kim <sbkim73@samsung.com>, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: samsung: drop unknown Kconfig symbol
Date: Thu, 24 Nov 2011 19:19:26 +0000 [thread overview]
Message-ID: <20111124191925.GC3395@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1322161754.25125.72.camel@x61.thuisdomein>
On Thu, Nov 24, 2011 at 08:09:14PM +0100, Paul Bolle wrote:
> - Kconfig"), both dated May 14, 2007. So I'm touching code here that has
> been unbuildable (in the mainline tree) for over four years. Isn't that
> in itself sufficient to drop this code (and the incomplete kbuild stuff
> supporting it)?
No, not really. None of the OpenMoko code (including GTA02) has ever
been usable in mainline as there's a reasonable patch stack for it out
of tree and the more of their code is in mainline the more likely it is
that that situation will improve. The cost of extra platforms is really
very low and people actually send me patches for the OpenMoko devices
from time to time (much more frequently than for most other boards) so
at least someone cares.
> > I'd suggest discussing this with the OpenMoko guys if you want to do it.
> Who would that be?
Google tells me http://www.openmoko.org is a good start - you might want
to ask on the openmoko-kernel list.
next prev parent reply other threads:[~2011-11-24 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 17:17 [PATCH] ASoC: samsung: drop unknown Kconfig symbol Paul Bolle
2011-11-24 17:22 ` Mark Brown
2011-11-24 19:09 ` Paul Bolle
2011-11-24 19:19 ` Mark Brown [this message]
2011-11-24 19:59 ` Paul Bolle
2011-11-24 22:22 ` Mark Brown
2011-11-25 9:41 ` Paul Bolle
2011-11-25 12:56 ` Mark Brown
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=20111124191925.GC3395@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=pebolle@tiscali.nl \
--cc=sbkim73@samsung.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