From: Jakub Kicinski <kuba@kernel.org>
To: Jerry.Ray@microchip.com
Cc: Vladimir Oltean <olteanv@gmail.com>,
krzysztof.kozlowski@linaro.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml
Date: Mon, 17 Oct 2022 12:19:28 -0700 [thread overview]
Message-ID: <20221017121928.36b582c3@kernel.org> (raw)
In-Reply-To: <20221017191311.mxkjfz75pgzbcwcz@skbuf>
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.
next prev parent reply other threads:[~2022-10-17 19:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:46 [net-next][PATCH v4] dt-bindings: dsa: Add lan9303 yaml Jerry Ray
2022-10-03 17:48 ` Krzysztof Kozlowski
2022-10-05 7:54 ` Krzysztof Kozlowski
2022-10-17 18:33 ` Jerry.Ray
2022-10-18 22:34 ` Krzysztof Kozlowski
2022-10-04 15:52 ` kernel test robot
2022-10-08 22:56 ` Vladimir Oltean
2022-10-09 15:20 ` Krzysztof Kozlowski
2022-10-09 22:22 ` Vladimir Oltean
2022-10-10 10:23 ` Krzysztof Kozlowski
2022-10-10 10:29 ` Vladimir Oltean
2022-10-17 18:51 ` Jerry.Ray
2022-10-17 19:13 ` Vladimir Oltean
2022-10-17 19:19 ` Jakub Kicinski [this message]
2022-10-17 20:00 ` Jerry.Ray
2022-10-17 21:02 ` Vladimir Oltean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017121928.36b582c3@kernel.org \
--to=kuba@kernel.org \
--cc=Jerry.Ray@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).