From: Jakub Kicinski <kuba@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Kyle Swenson <kyle.swenson@est.tech>,
"o.rempel@pengutronix.de" <o.rempel@pengutronix.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: pse-pd: tps23881: Fix the device ID check
Date: Mon, 12 Aug 2024 08:41:59 -0700 [thread overview]
Message-ID: <20240812084159.79e5baf3@kernel.org> (raw)
In-Reply-To: <20240810234556.4e3e9442@kmaincent-XPS-13-7390>
On Sat, 10 Aug 2024 23:45:56 +0200 Kory Maincent wrote:
> > The DEVID register contains two pieces of information: the device ID in
> > the upper nibble, and the silicon revision number in the lower nibble.
> > The driver should work fine with any silicon revision, so let's mask
> > that out in the device ID check.
> >
> > Fixes: 20e6d190ffe1 ("net: pse-pd: Add TI TPS23881 PSE controller driver")
> > Signed-off-by: Kyle Swenson <kyle.swenson@est.tech>
>
> Hello Kyle,
>
> In net subsystem when you send a fix you should use net prefix instead
> of net-next. Jakub, does Kyle have to send a new patch or can you deal with
> it?
>
> Thanks for your fix!
>
> Reviewed-by: Kory Maincent <kory.maincent@bootlin.com>
Ah, I'm pretty sure I already applied this. kernel.org infra has been
quite unreliable lately. Commit 89108cb5c285 ("net: pse-pd: tps23881:
Fix the device ID check"), indeed in net.
next prev parent reply other threads:[~2024-08-12 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 15:42 [PATCH net-next v2] net: pse-pd: tps23881: Fix the device ID check Kyle Swenson
2024-07-31 19:26 ` Thomas Petazzoni
2024-08-02 7:53 ` Oleksij Rempel
2024-08-10 21:45 ` Kory Maincent
2024-08-12 15:41 ` Jakub Kicinski [this message]
2024-08-14 9:21 ` Kory Maincent
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=20240812084159.79e5baf3@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kyle.swenson@est.tech \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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).