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 v3 3/3] net: dsa: microchip: replace unclear KSZ8830 strings
Date: Tue, 3 Sep 2024 15:20:16 +0000 [thread overview]
Message-ID: <03fa382f3469c0fa12d4051e23a7aebfa5c1d456.camel@microchip.com> (raw)
In-Reply-To: <20240903072946.344507-4-vtpieter@gmail.com>
On Tue, 2024-09-03 at 09:29 +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 ksz8830 with ksz88x3 for CHIP_ID definition and other
> strings. This due to KSZ8830 not being an actual switch but the Chip
> ID shared among KSZ8863/8873 switches, impossible to differentiate
> from their Chip ID or Revision ID registers.
>
> Now all KSZ*_CHIP_ID macros refer to actual, existing switches which
> removes confusion.
>
> Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch>
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
prev parent reply other threads:[~2024-09-03 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 7:29 [PATCH net-next v3 0/3] net: dsa: microchip: rename and clean ksz8 series files vtpieter
2024-09-03 7:29 ` [PATCH net-next v3 1/3] net: dsa: microchip: rename " vtpieter
2024-09-03 15:23 ` Arun.Ramadoss
2024-09-04 6:14 ` Pieter
2024-09-03 7:29 ` [PATCH net-next v3 2/3] net: dsa: microchip: clean up ksz8_reg definition macros vtpieter
2024-09-03 7:29 ` [PATCH net-next v3 3/3] net: dsa: microchip: replace unclear KSZ8830 strings vtpieter
2024-09-03 15:20 ` Arun.Ramadoss [this message]
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=03fa382f3469c0fa12d4051e23a7aebfa5c1d456.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
all inboxes | Powered by JetHome®