[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241122094210.5e643c1d@kmaincent-XPS-13-7390>
Date: Fri, 22 Nov 2024 09:42:10 +0100
From: Kory Maincent <kory.maincent@...tlin.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Andrew Lunn <andrew@...n.ch>, Oleksij Rempel <o.rempel@...gutronix.de>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Jonathan Corbet <corbet@....net>, Donald Hunter
<donald.hunter@...il.com>, Rob Herring <robh@...nel.org>, Andrew Lunn
<andrew+netdev@...n.ch>, Simon Horman <horms@...nel.org>, Heiner Kallweit
<hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, Liam Girdwood
<lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-doc@...r.kernel.org, Kyle Swenson
<kyle.swenson@....tech>, Dent Project <dentproject@...uxfoundation.org>,
kernel@...gutronix.de, Maxime Chevallier <maxime.chevallier@...tlin.com>
Subject: Re: [PATCH RFC net-next v3 25/27] dt-bindings: net: pse-pd:
microchip,pd692x0: Add manager regulator supply
Hello Krzysztof,
On Fri, 22 Nov 2024 07:58:26 +0100
Krzysztof Kozlowski <krzk@...nel.org> wrote:
> On 21/11/2024 15:42, Kory Maincent wrote:
> > From: Kory Maincent (Dent Project) <kory.maincent@...tlin.com>
> >
> > This patch adds the regulator supply parameter of the managers.
> > It updates also the example as the regulator supply of the PSE PIs
> > should be the managers itself and not an external regulator.
> >
> > Signed-off-by: Kory Maincent <kory.maincent@...tlin.com>
> > ---
> >
>
>
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
>
> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on some
> ancient tree (don't, instead use mainline) or work on fork of kernel
> (don't, instead use mainline). Just use b4 and everything should be
> fine, although remember about `b4 prep --auto-to-cc` if you added new
> patches to the patchset.
>
> You missed at least devicetree list (maybe more), so this won't be
> tested by automated tooling. Performing review on untested code might be
> a waste of time.
>
> Please kindly resend and include all necessary To/Cc entries.
> </form letter>
>
> ... unless you do not expect review.
Indeed I didn't expected binding reviews on this series that's why I did not add
you and devicetree mailing list to the CC. I would like to confirm the core PSE
design choices before that.
Maybe I should have notify it somewhere to avoid you these emails, sorry.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
Powered by blists - more mailing lists