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
| ||
|
Date: Wed, 02 Jun 2010 06:57:11 -0700 (PDT) From: David Miller <davem@...emloft.net> To: bhutchings@...arflare.com Cc: netdev@...r.kernel.org, linux-net-drivers@...arflare.com Subject: Re: [PATCH 00/12] sfc changes for 2.6.36 From: Ben Hutchings <bhutchings@...arflare.com> Date: Wed, 02 Jun 2010 14:52:26 +0100 > Did you apply patch 12 "sfc: Get port number from CS_PORT_NUM, not PCI > function number" to net-2.6? When you mix bug fixes and cleanups, I'm going to apply it all to net-next-2.6 You didn't even specify an intended destination in your subject lines, so you leave it entirely open for interpretation and my choice. So, if you want a bug fix added to net-2.6, tossing it into a series which is not wholly appropriate for net-next-2.6 is not that way to accomplish that. The way to do it is: 1) Submit the bug fix, explicitly state "[PATCH net-2.6 xxx] " in your subject line. 2) Prepare your net-next-2.6 changes on top of that, and do one of two things: a) Explicitly state in your patch series in the "[PATCH net-next-2.6 0/xxx] " posting "this depends upon the bug fixes posted in the series XXX posted earlier. b) Wait for the bug fix to reach net-next-2.6 when I do a merge, then post your series. Otherwise you make life way to miserable and complicated for me, the one who has to review and integrate all of your work. Thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists