[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240711084300.GA8788@kernel.org>
Date: Thu, 11 Jul 2024 09:43:00 +0100
From: Simon Horman <horms@...nel.org>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
thomas.petazzoni@...tlin.com,
Oleksij Rempel <o.rempel@...gutronix.de>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH v2 1/2] net: pse-pd: Do not return EOPNOSUPP if config is
null
On Wed, Jul 10, 2024 at 01:42:30PM +0200, Kory Maincent wrote:
> For a PSE supporting both c33 and PoDL, setting config for one type of PoE
> leaves the other type's config null. Currently, this case returns
> EOPNOTSUPP, which is incorrect. Instead, we should do nothing if the
> configuration is empty.
>
> Signed-off-by: Kory Maincent <kory.maincent@...tlin.com>
> Fixes: d83e13761d5b ("net: pse-pd: Use regulator framework within PSE framework")
> ---
>
> Changes in v2:
> - New patch to fix dealing with a null config.
Hi Kory,
A few thing from a process perspective:
1. As fixes, with fixes tags (good!), this patchset seems like it is
appropriate for net rather than net-next. And indeed it applies
to net but not net-next. However, the absence of a target tree
confuses our CI which failed to apply the patchset to net-next.
Probably this means it should be reposted, targeted at net.
Subject: [Patch v3 net x/y] ...
See: https://docs.kernel.org/process/maintainer-netdev.html
2. Please provide a cover letter for patch sets with more than one
(but not just one) patch. That provides an overview of how
the patches relate to each other. And a convenient anchor for
feedback such as point 1 above.
...
Powered by blists - more mailing lists