linux-kernel - Re: How to remove 2000+ lines from 400+ defconfig files?

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-next>] [day] [month] [year] [list]

Date:	Tue, 15 Nov 2011 14:14:15 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: How to remove 2000+ lines from 400+ defconfig files?

On Tue, 15 Nov 2011, Paul Bolle wrote:

> Michal, Jiri,

[ adding LKML to CC ]

> 0) While, slowly, working through the accumulated Kconfig cruft I
> noticed quite a number of outdated (Kconfig) macros in (almost) all
> defconfig files. A few days ago I counted 161 outdated Kconfig macros,
> totaling 2189 lines in 426 defconfig files. Please see below for a draft
> commit log, with a sort-of-impressive stat. (A few of these macros are
> still used in the code. I already sent out messages to try to clean up
> that too.)
> 
> 1) They create false negatives while grepping for outdated stuff. At
> some point I decided to write a script to remove all of them.
> 
> 2) Is it worth the trouble to try to remove all that from the mainline
> tree? If it is, how would you propose I try to get something like this
> commit merged?

I am fine taking those through trivial.git and handling the fallout. The 
only ones I'd have objections to taking immediately are those which are 
actually still referenced somewhere in the code.
For those, either taking them through appropriate maintainers, or having 
their Acked-by would be required.

Thanks,

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