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]

Date:	Mon, 31 Oct 2011 11:59:59 +0100
From:	Jesper Nilsson <jesper.nilsson@...s.com>
To:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>
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

Sorry for the late answer, I've been in-flight my self.

On Fri, Oct 14, 2011 at 09:11:01PM +0200, Valdis.Kletnieks@...edu wrote:
> 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?

You are of course correct that the driver patches should be
ones that add the Kconfigs.

The drivers have been in-flight for quite a while, but without any
push from us, I'll try to give it some love, and at least get it into
a separate tree.

> (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)

Ok, let's do it the right way and remove them now, and I can re-add
them in the same tree.

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@...s.com
--
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/