From: Jakub Kicinski <kuba@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org,
Russell King <rmk+kernel@armlinux.org.uk>,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next] net: phy: vitesse: add inband caps and configuration
Date: Fri, 13 Mar 2026 18:59:18 -0700 [thread overview]
Message-ID: <20260313185918.74ba4168@kernel.org> (raw)
In-Reply-To: <20260313-unloving-ambiguous-a6f492db06a9@spud>
On Fri, 13 Mar 2026 09:50:09 +0000 Conor Dooley wrote:
> > Here is the summary with links:
> > - [net-next] net: phy: vitesse: add inband caps and configuration
> > https://git.kernel.org/netdev/net-next/c/6e263aadbaf2
>
> Hmm, should this have been done? Charles proposed a different patch in
> this thread that got posted here: abMa8e_2fjRkeOix@shell.armlinux.org.uk
> It seems to have less chance for impacting other ethernet controller
> drivers negatively.
Sorry, we've been getting 150 patches a day this week.
A bit hard to keep track. If y'all could please post
a necessary follow up I'd appreciate.
prev parent reply other threads:[~2026-03-14 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 1:07 [PATCH net-next] net: phy: vitesse: add inband caps and configuration Russell King (Oracle)
2026-03-11 9:22 ` Conor Dooley
2026-03-11 14:01 ` Geert Uytterhoeven
2026-03-11 14:26 ` Russell King (Oracle)
2026-03-11 14:43 ` Geert Uytterhoeven
2026-03-11 14:54 ` Russell King (Oracle)
2026-03-11 15:04 ` Conor Dooley
2026-03-11 15:28 ` Charles Perry
2026-03-11 15:38 ` Conor Dooley
2026-03-11 14:02 ` Geert Uytterhoeven
2026-03-13 1:00 ` patchwork-bot+netdevbpf
2026-03-13 9:50 ` Conor Dooley
2026-03-14 1:59 ` Jakub Kicinski [this message]
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=20260313185918.74ba4168@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.