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: Fri, 25 Nov 2011 12:56:39 +0000 [thread overview]
Message-ID: <20111125125638.GC5315@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1322214066.25125.124.camel@x61.thuisdomein>
On Fri, Nov 25, 2011 at 10:41:06AM +0100, Paul Bolle wrote:
> On Thu, 2011-11-24 at 22:22 +0000, Mark Brown wrote:
> > > But - repeating my message - none of those patches made the code in the
> > > mainline tree buildable.
> > Which is a problem because...
> Because in mainline there's code that can't be built and can't be run.
Which is a problem because...
> > (and note that you mean "selectable in
> > Kconfig" here).
> The Kconfig files in mainline don't define a symbol MACH_NEO1973_GTA01.
Yes, that would be an example fo the sort of thing that would make it
impossible to select in Kconfig.
> My claim is just that code that has been unbuildable in the mainline
> tree for over four years can be removed. But, as I said in a previous
> message, I don't have any stake in the GTA01 code. I don't mind
> revisiting all this at (say) the end of the v3.3 merge period.
No. What I'm telling you is not to revisit this, this is not a helpful
change.
prev parent reply other threads:[~2011-11-25 12:56 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
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 [this message]
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=20111125125638.GC5315@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