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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 17 Oct 2022 12:19:28 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Jerry.Ray@...rochip.com Cc: Vladimir Oltean <olteanv@...il.com>, krzysztof.kozlowski@...aro.org, andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml On Mon, 17 Oct 2022 22:13:11 +0300 Vladimir Oltean wrote: > The portion I highlighted of the change you're making includes your name > into the output of $(./scripts/get_maintainer.pl drivers/net/dsa/lan9303-core.c). > In other words, you're voluntarily subscribing to the responsibility of > being a maintainer for the driver, getting emails from other developers, > reviewing patches. Furthermore, you also maintain the code in the stable > trees, hence your name also gets propagated there so people who use > those kernels can report problems to you. > > The MAINTAINERS entry for lan9303 needs to go to the "net" tree, from > where it can be backported. This covers the driver + schema files as > they currently are. The change of the .txt to the .yaml schema then > comes on top of that (and on "net-next"). And FWIW net gets merged into net-next every Thu so (compared to how long this patch had been in review) it won't be a large delay to wait for the MAINTAINERS patch to propagate.
Powered by blists - more mailing lists