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] [day] [month] [year] [list]
Date:	Fri, 25 Nov 2011 12:56:39 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Paul Bolle <pebolle@...cali.nl>
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 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.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ