| 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 Mar 2011 21:49:10 -0800 (PST) From: David Miller <davem@...emloft.net> To: fubar@...ibm.com CC: netdev@...r.kernel.org Subject: bonding... Hey, if someone could step up and help with bonding maintainence in some tangible way, I'd really appreciate it. Currently the situation is that many people work on bonding patches, and whilst I do try and wait for some ACKs to arrive, I am the person who has to sort out when changes are ready, decide to apply them, and poke for review when things fall through the cracks. Sometimes patches go for weeks without ACKs, and in that situation I have to either try to understand the changes myself, or wait potentially forever for someone with bonding knowledge to take a good look at the patch and properly review it. It was nearly 2 weeks before Oleg V. Ukhno's 802.3ad round-robin patch got looked at by anyone with bonding knowledge. And it only happened because I got tired of seeing his poor patch rot in patchwork and had to explicitly asked for review the other day. This is unacceptable, people are submitting multiple bonding patches every single day now. It needs a clueful bonding person looking at these submissions on a constant basis. This is a serious problem and is backlogging the netdev patch queue. So if someone would become an active bonding patch-accumulator, and send me sets of patches that are ready to apply, I would really appreciate it. 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