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 v4 1/3] net: dsa: microchip: rename ksz8 series files
Date: Wed, 4 Sep 2024 07:59:37 +0000 [thread overview]
Message-ID: <ef164ccdc7ba7baf5b10f33d13c0be7e7e9ca780.camel@microchip.com> (raw)
In-Reply-To: <20240904062749.466124-2-vtpieter@gmail.com>
On Wed, 2024-09-04 at 08:27 +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>
>
> The first KSZ8 series implementation was done for a KSZ8795 device
> but
> since several other KSZ8 devices have been added. Rename these files
> to adhere to the ksz8 naming convention as already used in most
> functions and the existing ksz8.h; add an explanatory note.
>
> Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch>
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
next prev parent reply other threads:[~2024-09-04 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:27 [PATCH net-next v4 0/3] net: dsa: microchip: rename and clean ksz8 series files vtpieter
2024-09-04 6:27 ` [PATCH net-next v4 1/3] net: dsa: microchip: rename " vtpieter
2024-09-04 7:59 ` Arun.Ramadoss [this message]
2024-09-04 6:27 ` [PATCH net-next v4 2/3] net: dsa: microchip: clean up ksz8_reg definition macros vtpieter
2024-09-04 6:27 ` [PATCH net-next v4 3/3] net: dsa: microchip: replace unclear KSZ8830 strings vtpieter
2024-09-06 7:50 ` [PATCH net-next v4 0/3] net: dsa: microchip: rename and clean ksz8 series files 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=ef164ccdc7ba7baf5b10f33d13c0be7e7e9ca780.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