From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <olteanv@gmail.com>, <davem@davemloft.net>,
<linux@armlinux.org.uk>, <Woojung.Huh@microchip.com>,
<f.fainelli@gmail.com>, <kuba@kernel.org>, <vtpieter@gmail.com>,
<UNGLinuxDriver@microchip.com>, <edumazet@google.com>,
<pabeni@redhat.com>
Cc: <o.rempel@pengutronix.de>, <pieter.van.trappen@cern.ch>,
<Tristram.Ha@microchip.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 3/3] net: dsa: microchip: replace unclear KSZ8830 strings
Date: Mon, 2 Sep 2024 03:32:15 +0000 [thread overview]
Message-ID: <efce22790603dff9cff21eaf39f74b6a4b5d4a97.camel@microchip.com> (raw)
In-Reply-To: <20240830141250.30425-4-vtpieter@gmail.com>
Hi Pieter,
On Fri, 2024-08-30 at 16:12 +0200, vtpieter@gmail.com wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> From: Pieter Van Trappen <pieter.van.trappen@cern.ch>
>
> Replace uppercase KSZ8830 with KSZ8863
Since KSZ8863/73 sharing same chip id, replacing KSZ8830 with KSZ8863
is somewhat confusing. Can you elaborate here. I believe, it should
KSZ88X3_CHIP_ID.
next prev parent reply other threads:[~2024-09-02 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:12 [PATCH net-next v2 0/3] net: dsa: microchip: rename and clean ksz8 series files vtpieter
2024-08-30 14:12 ` [PATCH net-next v2 1/3] net: dsa: microchip: rename " vtpieter
2024-09-02 2:56 ` Arun.Ramadoss
2024-09-02 10:08 ` Pieter
2024-09-02 14:30 ` Arun.Ramadoss
2024-08-30 14:12 ` [PATCH net-next v2 2/3] net: dsa: microchip: clean up ksz8_reg definition macros vtpieter
2024-09-02 3:25 ` Arun.Ramadoss
2024-08-30 14:12 ` [PATCH net-next v2 3/3] net: dsa: microchip: replace unclear KSZ8830 strings vtpieter
2024-09-02 3:32 ` Arun.Ramadoss [this message]
2024-09-02 10:14 ` Pieter
2024-09-02 14:48 ` Arun.Ramadoss
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=efce22790603dff9cff21eaf39f74b6a4b5d4a97.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pieter.van.trappen@cern.ch \
--cc=vtpieter@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox