linux-kernel - Re: [PATCH] ASoC: samsung: drop unknown Kconfig symbol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1322161754.25125.72.camel@x61.thuisdomein>
Date:	Thu, 24 Nov 2011 20:09:14 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Jassi Brar <jassisinghbrar@...il.com>,
	Sangbeom Kim <sbkim73@...sung.com>, Liam Girdwood <lrg@...com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: samsung: drop unknown Kconfig symbol

On Thu, 2011-11-24 at 17:22 +0000, Mark Brown wrote:
> On Thu, Nov 24, 2011 at 06:17:17PM +0100, Paul Bolle wrote:
> There's people somewhat actively working on the OpenMoko devices out of
> tree (and I personally have a GTA01) and I'd rather not do anything that
> causes any more hassle for them.

I don't own a GTA01. Neither do I like to cause hassle for the people
working on OpenMoko.

But the history of the code my patch drops, seems to start with
(mainline) commits 74930bb6db ("[ALSA] ASoC S3C24xx machine drivers -
Openmoko Neo1973") and 80ab1c0e9e ("[ALSA] ASoC S3C24xx machine drivers
- 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)?

> I'd suggest discussing this with the OpenMoko guys if you want to do it.

Who would that be?


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/