| 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
| ||
|
Message-ID: <457B30EC.8020805@s5r6.in-berlin.de> Date: Sat, 09 Dec 2006 22:55:56 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Pekka Enberg <penberg@...helsinki.fi> CC: "Robert P. J. Day" <rpjday@...dspring.com>, Linux kernel mailing list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] kcalloc: Re-order the first two out-of-order args to kcalloc(). Pekka Enberg wrote: > On 12/9/06, Robert P. J. Day <rpjday@...dspring.com> wrote: >> normally what i would do but, in the case of that patch, there are >> five files affected, *all* of which are in totally different >> subsystems (macintosh, net, scsi, usb, sunrpc). are you suggesting >> that up to 5 different people be CC'ed? >> >> and what about source-wide aesthetic changes that might touch dozens >> or hundreds of files? > > Well, it depends. There are no fixed rules in the art of patch > feeding. FWIW, I probably would send this patch just to akpm too. Yes, patches like this one are no big deal. But being involved in subsystem maintenance, I find patches split up per subsystem much easier to handle. Ccing the subsystem maintainers doen't make much sens if you don't split the patch for them to integrate separately. -- Stefan Richter -=====-=-==- ==-- -=--= http://arcgraph.de/sr/ - 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/
Powered by blists - more mailing lists