All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	David Miller <davem@davemloft.net>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	Michael Klein <michael@fossekall.de>,
	Realtek linux nic maintainers <nic_swsd@realtek.com>,
	Aleksander Jan Bajkowski <olek2@wp.pl>,
	Fabio Baltieri <fabio.baltieri@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP)
Date: Sat, 10 Jan 2026 14:30:18 -0800	[thread overview]
Message-ID: <20260110143018.56a19502@kernel.org> (raw)
In-Reply-To: <aWKxrOfWncySwz69@makrotopia.org>

On Sat, 10 Jan 2026 20:08:12 +0000 Daniel Golle wrote:
> > > This series silently conflicts with Daniel's changes. I wasn't clear
> > > whether the conclusion here:
> > > https://lore.kernel.org/all/1261b3d5-3e09-4dd6-8645-fd546cbdce62@gmail.com/
> > > is that we shouldn't remove the define or Daniel's changes are good 
> > > to go in.. Could y'all spell out for me what you expect?  
> > 
> > I'm fine with replacing RTL_VND2_PHYSR with RTL_PHYSR, as proposed by Daniel.
> > However, as this isn't a fully trivial change, I'd like to avoid this change
> > in my series, and leave it to Daniel's series. Means he would have to add
> > the conversion of the call I just add.
> > Which series to apply first depends on whether Daniel has to send a new version,
> > or whether it's fine as-is. There was a number of comments, therefore I'm not
> > 100% sure.  
> 
> Imho it makes sense to merge RTL8127ATF first and I'll resend my current
> series. There was a typo in one of the commit messages, but more than that
> I think it does make sense to merge the non-controveral hardware addition
> before applying any potentially disruptive stuff which affects practically
> all PHYs supported by the driver (doesn't mean that I expect any disruption
> what-so-ever, but as a matter of principle it just seems right to do it
> that way around).

SG! Thanks for breaking the tie.

  reply	other threads:[~2026-01-10 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-10 15:12 [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP) Heiner Kallweit
2026-01-10 15:14 ` [PATCH net-next v2 1/2] net: phy: realtek: add dummy PHY driver for RTL8127ATF Heiner Kallweit
2026-01-10 15:15 ` [PATCH net-next v2 2/2] r8169: add support for RTL8127ATF (Fiber SFP) Heiner Kallweit
2026-01-11 21:05   ` Fabio Baltieri
2026-01-10 18:48 ` [PATCH net-next v2 0/2] r8169: add support for RTL8127ATF (10G Fiber SFP) Jakub Kicinski
2026-01-10 20:03   ` Heiner Kallweit
2026-01-10 20:08     ` Daniel Golle
2026-01-10 22:30       ` Jakub Kicinski [this message]
2026-01-13  3:30 ` 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=20260110143018.56a19502@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fabio.baltieri@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=michael@fossekall.de \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=olek2@wp.pl \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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 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.