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: <20130415151132.GJ11974@axis.com>
Date:	Mon, 15 Apr 2013 17:11:32 +0200
From:	Jesper Nilsson <jesper.nilsson@...s.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Jesper Nilsson <jespern@...s.com>,
	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	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 Sat, Mar 23, 2013 at 02:14:46PM +0100, Paul Bolle wrote:
> Jesper,
> 
> On Mon, 2011-10-31 at 11:59 +0100, Jesper Nilsson wrote:
> > Ok, let's do it the right way and remove them now, and I can re-add
> > them in the same tree.
> 
> The patch at the start of this (old) thread still applies on top of
> v3.9-rc3. Do you still intend to remove the cris Kconfig symbols unused
> in mainline?
> 
> (Note that there's a second order effect to this patch:
> ETRAX_ETHERNET_IFACE0, and ETRAX_ETHERNET_IFACE1, and ETRAX_SERIAL_PORT4
> could also be dropped. I'm happy to submit a patch with those included
> too.)

Yes, please do, I just get mangled versions when I try to dig
the old patch out from the web.

> Paul Bolle

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