From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: andrew@lunn.ch, kuba@kernel.org, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
kory.maincent@bootlin.com, vadim.fedorenko@linux.dev,
maxime.chevallier@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 1/2] net: ethtool: reject an out of range hwtstamp provider index
Date: Tue, 29 Sep 2026 02:40:14 +0000 [thread overview]
Message-ID: <179064961404.229594.5490433720039637350.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925135237.3432266-2-nb@tipi-net.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Sep 2026 15:52:35 +0200 you wrote:
> A provider index of 0xFFFFFFFF picks a provider on hardware that has
> none. phc_index is an int where -1 means no PHC, and the u32 from user
> space ends up as -1, so the two match.
>
> TSINFO_GET uses -1 for "no provider requested" and answers with the
> default provider instead of an error.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: ethtool: reject an out of range hwtstamp provider index
https://git.kernel.org/netdev/net-next/c/67da3009384f
- [net,v3,2/2] net: ethtool: let tsconfig reach a PHY-only timestamp provider
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-29 2:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260925135237.3432266-1-nb@tipi-net.de>
2026-09-25 13:52 ` Nicolai Buchwitz
2026-09-25 13:55 ` Kory Maincent
2026-09-25 14:07 ` Nicolai Buchwitz
2026-09-25 17:57 ` Kory Maincent
2026-09-29 2:30 ` patchwork-bot+netdevbpf
2026-09-29 2:40 ` patchwork-bot+netdevbpf [this message]
2026-09-25 13:52 ` [PATCH net v3 2/2] net: ethtool: let tsconfig reach a PHY-only timestamp provider Nicolai Buchwitz
2026-09-26 13:54 ` netdev-bot+sashiko
2026-09-26 17:53 ` Nicolai Buchwitz
2026-09-26 18:03 ` Maxime Chevallier
2026-09-26 18:11 ` Nicolai Buchwitz
2026-09-29 2:29 ` Jakub Kicinski
2026-09-26 18:04 ` Maxime Chevallier
2026-09-27 16:00 ` 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=179064961404.229594.5490433720039637350.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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
all inboxes | Powered by JetHome®