linux-kernel - Re: how to properly post/disseminate kernel cleanup/janitorial possibilities?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.0904291400200.5012@wotan.suse.de>
Date:	Wed, 29 Apr 2009 14:01:12 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:	Johannes Weiner <hannes@...xchg.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: how to properly post/disseminate kernel cleanup/janitorial
 possibilities?

On Tue, 28 Apr 2009, Robert P. J. Day wrote:

> > > Perhaps Jiri can pick up some of the patches that remove stale 
> > > config symbols, correct typos etc.
> > Absolutely. I'll happily apply anything trivial enough (typo fixes,
> > removal of obviously unused symbols/config options, etc).
>   the *problem* is that, sometimes, it's not obvious.  as in, when a
> Kconfig file has a pile of unused config options but it turns out that
> those were added for future consideration to match up with code that
> hasn't been added yet and the subsystem maintainer knows about it but
> wants it to stay (IMHO, a really bad idea -- adding kernel features in
> incomplete pieces, but whatever).

Hmm ... do you have any particular outstanding examples of this?

-- 
Jiri Kosina
SUSE Labs
--
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/