From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Christian Eggers <ceggers@arri.de>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Juergen Beisert <jbe@pengutronix.de>, Stefan Roese <sr@denx.de>,
Juergen Borleis <kernel@pengutronix.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] dsa: lan9303: consistent naming for PHY address parameter
Date: Mon, 8 Jul 2024 09:33:16 -0700 [thread overview]
Message-ID: <20240708093316.535b16ab@kernel.org> (raw)
In-Reply-To: <20240708121352.gnhhjuvvoxpjhtpv@skbuf>
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.
next prev parent reply other threads:[~2024-07-08 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:57 [PATCH net 1/2] dsa: lan9303: Fix mapping between DSA port number and PHY address Christian Eggers
2024-07-03 14:57 ` [PATCH net 2/2] dsa: lan9303: consistent naming for PHY address parameter Christian Eggers
2024-07-03 16:08 ` Michal Kubiak
2024-07-04 14:51 ` Florian Fainelli
2024-07-05 2:20 ` Jakub Kicinski
2024-07-08 12:13 ` Vladimir Oltean
2024-07-08 16:33 ` Jakub Kicinski [this message]
2024-07-03 16:04 ` [PATCH net 1/2] dsa: lan9303: Fix mapping between DSA port number and PHY address Michal Kubiak
2024-07-04 14:50 ` Florian Fainelli
2024-07-04 17:29 ` Vladimir Oltean
2024-07-05 2: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=20240708093316.535b16ab@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jbe@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sr@denx.de \
/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.