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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.2.00.0904281024150.5012@wotan.suse.de>
Date:	Tue, 28 Apr 2009 10:25:17 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Johannes Weiner <hannes@...xchg.org>
Cc:	"Robert P. J. Day" <rpjday@...shcourse.ca>,
	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, Johannes Weiner wrote:

> > long story short, i have a *pile* of scripts and sub-scripts i'm happy 
> > to run and post the results of since it takes practically zero time on 
> > my part, i'm just open to what folks think is the most productive way 
> > to do that, and also for any other scanning i can add since, by now, 
> > any other patterns to scan for would just represent adding a line or 
> > two to a script.
> >  thoughts?
> Yes.  I wonder why you take the time to generate the output and email
> it but then stop there instead of just sending patches?
>
> grep -A5 TRIVIAL MAINTAINERS
> 
> 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).

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/