| 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: <20131029.002317.345164763391263319.davem@davemloft.net> Date: Tue, 29 Oct 2013 00:23:17 -0400 (EDT) From: David Miller <davem@...emloft.net> To: hayeswang@...ltek.com Cc: netdev@...r.kernel.org, nic_swsd@...ltek.com, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org Subject: Re: [PATCH 0/5] r8152 bug fixes From: Hayes Wang <hayeswang@...ltek.com> Date: Mon, 28 Oct 2013 19:58:09 +0800 > These could fix some driver issues. > > Hayes Wang (5): > net/usb/r8152: fix tx/rx memory overflow > net/usb/r8152: make sure the tx checksum setting is correct > net/usb/r8152: modify the tx flow > net/usb/r8152: fix incorrect type in assignment > net/usb/r8152: code adjust These are not bug fixes, some of them are just cleanups. It is inappropriate to mix real bug fixes and non-bug fixes into a patch series. You must send purely the bug fixes for 'net' tree, and then later the code cleanups and other changes targetting the 'net-next' tree. Also, from patch #5: ==================== -Something else ==================== That is completely unacceptable. You must say what changes you are making, the above says nothing to me nor the person reading your commit messages in the future. In general, your commit messages are poorly written in that they contain not enough information for the person trying to understand your patches at all. -- 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