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: <20230327190334.6c5bcf87@kernel.org> Date: Mon, 27 Mar 2023 19:03:34 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Arınç ÜNAL <arinc.unal@...nc9.com> Cc: Vladimir Oltean <olteanv@...il.com>, Sean Wang <sean.wang@...iatek.com>, Landen Chao <Landen.Chao@...iatek.com>, DENG Qingfang <dqfext@...il.com>, Andrew Lunn <andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Matthias Brugger <matthias.bgg@...il.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Russell King <linux@...linux.org.uk>, René van Dorst <opensource@...rst.com>, Russell King <rmk+kernel@...linux.org.uk>, Ilya Lipnitskiy <ilya.lipnitskiy@...il.com>, Richard van Schagen <richard@...terhints.com>, Richard van Schagen <vschagen@...com>, Frank Wunderlich <frank-w@...lic-files.de>, erkin.bozoglu@...ont.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org Subject: Re: [PATCH net 4/7] net: dsa: mt7530: set both CPU port interfaces to PHY_INTERFACE_MODE_NA On Tue, 28 Mar 2023 00:57:57 +0300 Arınç ÜNAL wrote: > I don't appreciate your consistent use of the word "abuse" on my > patches. I'm by no means a senior C programmer. I'm doing my best to > correct the driver. > > Thank you for explaining the process of phylink with DSA, I will adjust > my patches accordingly. > > I suggest you don't take my patches seriously for a while, until I know > better. Maybe my bad, I should have sent you a note on your previous series already. The patches may be fine, but the commit messages need to do a better job of describing what the goal of the change is, functionally. For fixes the bar is even higher because, as Vladimir points out, commit messages for fixes need to explain what user visible problem the patch is resolving. Think of it as a letter to a person using the switch who hits a problem and wants to look thru the upstream commits to see if it's already fixed.
Powered by blists - more mailing lists