linux-kernel - Re: [PATCH 21/21] cris: drop unused Kconfig symbols

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: <14215.1318619461@turing-police.cc.vt.edu>
Date:	Fri, 14 Oct 2011 15:11:01 -0400
From:	Valdis.Kletnieks@...edu
To:	Jesper Nilsson <jesper.nilsson@...s.com>
Cc:	Paul Bolle <pebolle@...cali.nl>, Mikael Starvik <starvik@...s.com>,
	linux-cris-kernel <linux-cris-kernel@...s.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 21/21] cris: drop unused Kconfig symbols

On Fri, 14 Oct 2011 15:33:54 +0200, Jesper Nilsson said:
> Hmmm... NAK on that. Lots of these configs are actually used, but in drivers
> not upstream yet (serial port, ethernet and usb drivers for ARTPEC-3).

Shouldn't the patches that upstream those drivers be the ones to add the
Kconfig glue?  Or is this a case of "in-flight driver" where the submission is
literally in the middle of getting merged so some parts have landed and some
haven't yet, and all will be good in the next merge cycle?

(Personally, I'm tending towards unless it's going to be in linux-next within
the next month or so, pull the Kconfig variables out and the driver can re-add
them when it actually lands)


Content of type "application/pgp-signature" skipped