linux-kernel - Re: [PATCH 4/4] drivers/media/video: Remove dead CONFIG_OLPC_X0

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]

Message-ID: <20100719163930.6c3333a7@bike.lwn.net>
Date:	Mon, 19 Jul 2010 16:39:30 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Christian Dietrich <qy03fugy@...d.informatik.uni-erlangen.de>
Cc:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Tejun Heo <tj@...nel.org>, linux-media@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	vamos-dev@...informatik.uni-erlangen.de
Subject: Re: [PATCH 4/4] drivers/media/video: Remove dead CONFIG_OLPC_X0_1

On Wed, 14 Jul 2010 15:21:48 +0200
Christian Dietrich <qy03fugy@...d.informatik.uni-erlangen.de> wrote:

> CONFIG_OLPC_X0_1 doesn't exist in Kconfig and is never defined anywhere
> else, therefore removing all references for it from the source code.

That symbol is, needless to say, an OLPC thing; it's in their
repository.  I do think they plan to upstream all of that at some
point, but I think they're a little busy at the moment.

Deleting this code will increase the delta between the OLPC and
mainline trees.  My preference would be for that not to happen.  If it
does, though, life will obviously go on, and this code can be restored
when the rest is upstreamed.  If you must do that, though, could I ask
that you preserve the CONFIG_OLPC_XO_1 version of the code, which is
the version which has traditionally been in the mainline?

jon
--
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/