linux-kernel - Re: Proper patch posting question

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

Date:	Sat, 11 Nov 2006 19:20:59 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Burman Yan <yan_952@...mail.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Proper patch posting question


> I made a patch that replaces kmalloc+memset with kzalloc. The changes are in
> many
> different places in the kernel, but most of them are trivial. The whole patch
> is about
> 360Kb. The less trivial parts that make more changes than just replacing
> kmalloc with
> kzalloc and removing the memset are in different patches that I will send to
> the proper
> maintainers.
> My question is what would be the right way to post the trivial changes?
> The way I see, I have a few options:
> 1) Post the entire patch on lkml

Split by complexity, then by size (IIRC LKML allows up to 100 KB mails, 
but keep it smaller preferably because when it gets tedious to look at a 
mail, continue 'somewhere in the middle' is hard - find the spot first)

> 2) Split the patch into subsystems and post the smaller parts on lkml

Subsystems is also a good idea.

> 3) Send the patch to trivial@...nel.org

I'd go for lkml + trivial.


	-`J'
-- 
-
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/