[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240708093316.535b16ab@kernel.org>
Date: Mon, 8 Jul 2024 09:33:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Christian Eggers <ceggers@...i.de>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>, "David S . Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Juergen Beisert <jbe@...gutronix.de>, Stefan Roese
<sr@...x.de>, Juergen Borleis <kernel@...gutronix.de>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net 2/2] dsa: lan9303: consistent naming for PHY address
parameter
On Mon, 8 Jul 2024 15:13:52 +0300 Vladimir Oltean wrote:
> On Thu, Jul 04, 2024 at 07:20:34PM -0700, Jakub Kicinski wrote:
> > On Wed, 3 Jul 2024 16:57:18 +0200 Christian Eggers wrote:
> > > Name it 'addr' instead of 'port' or 'phy'.
> >
> > Unfortunately the fix has narrowly missed today's PR.
> > Please resend this for net-next in a week+.
>
> How does this work? You're no longer taking 'net' patches through the
> 'net' tree in the last week before the net-next pull request?
The fix has narrowly missed the PR, IOW patch 1 has missed the PR.
Patch 2 is not a fix.
Powered by blists - more mailing lists