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: Mon, 07 May 2012 13:44:51 -0400 (EDT) From: David Miller <davem@...emloft.net> To: erwanaliasr1@...il.com Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org, tshimizu818@...il.com Subject: Re: [PATCH] pch_gbe: Adding read memory barriers From: Erwan Velu <erwanaliasr1@...il.com> Date: Mon, 07 May 2012 19:39:47 +0200 > Please find attached First of all, for a patch which is not accepted yet you do not CC: stable. Second of all, do not put text in the main body of your email which is unrelated to the patch and should not end up in the commit message. Instead, post your patch to the appropriate primary mailing lists, and if it's accepted it can then be submitted to -stable at some later time. Your patch posting email should be composed purely of the commit log message in the message body, followed by the actual patch. Otherwise the maintainer that applies your patch has to edit out all of this other flowery text that is unrelated to the commit and that makes more work for them. -- 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