From: Nicolai Buchwitz <nb@tipi-net.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev-bot+sashiko@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
richardcochran@gmail.com, kory.maincent@bootlin.com,
vadim.fedorenko@linux.dev, jjc@jclark.com,
florian.fainelli@broadcom.com, opendmb@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: don't require the hwtstamp NDOs when a PHY provides timestamping
Date: Tue, 22 Sep 2026 09:12:14 +0200 [thread overview]
Message-ID: <3663f91fa60a78f8eeadb6983cf0d70f@tipi-net.de> (raw)
In-Reply-To: <20260921163746.5d5d0070@kernel.org>
On 22.9.2026 01:37, Jakub Kicinski wrote:
> On Mon, 21 Sep 2026 12:23:37 +0200 Nicolai Buchwitz wrote:
> [...]
>> No, IMHO not here. It would change change behaviour that never worked.
>> Thus I would suggest fixing this with a follow-up to net-next.
>
> Not sure I agree that it's separate but whatever, I don't want the
> ioctl
> fix to miss rc5.
>
> I'd prefer the netlink fix to also target net, tho. Netlink
> functionality should match the IOCTL, targeting -next would put user
> space in an awkward position when deciding between the two.
Ack, see
https://lore.kernel.org/netdev/20260922070813.1458713-1-nb@tipi-net.de/
Thanks
Nicolai
next prev parent reply other threads:[~2026-09-22 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:55 Nicolai Buchwitz
2026-09-18 23:25 ` Kory Maincent
2026-09-21 9:57 ` netdev-bot+sashiko
2026-09-21 10:23 ` Nicolai Buchwitz
2026-09-21 23:37 ` Jakub Kicinski
2026-09-22 7:12 ` Nicolai Buchwitz [this message]
2026-09-21 23:40 ` patchwork-bot+netdevbpf
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=3663f91fa60a78f8eeadb6983cf0d70f@tipi-net.de \
--to=nb@tipi-net.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=jjc@jclark.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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®