netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Christian Eggers <ceggers@arri.de>, Andrew Lunn <andrew@lunn.ch>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Juergen Beisert <jbe@pengutronix.de>, Stefan Roese <sr@denx.de>,
	Juergen Borleis <kernel@pengutronix.de>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] dsa: lan9303: consistent naming for PHY address parameter
Date: Thu, 4 Jul 2024 16:51:10 +0200	[thread overview]
Message-ID: <2b0f7253-685f-4af9-853d-66060be69489@gmail.com> (raw)
In-Reply-To: <20240703145718.19951-2-ceggers@arri.de>



On 7/3/2024 3:57 PM, Christian Eggers wrote:
> Name it 'addr' instead of 'port' or 'phy'.
> 
> Signed-off-by: Christian Eggers <ceggers@arri.de>

Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
-- 
Florian

  parent reply	other threads:[~2024-07-04 14:51 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 [this message]
2024-07-05  2:20   ` Jakub Kicinski
2024-07-08 12:13     ` Vladimir Oltean
2024-07-08 16:33       ` Jakub Kicinski
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=2b0f7253-685f-4af9-853d-66060be69489@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ceggers@arri.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jbe@pengutronix.de \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).