From: Paolo Abeni <pabeni@redhat.com>
To: "Ramón Nordin Rodriguez" <ramon.nordin.rodriguez@ferroamp.se>,
"Parthiban Veerasooran" <Parthiban.Veerasooran@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horatiu.vultur@microchip.com, Woojung.Huh@microchip.com,
Nicolas.Ferre@microchip.com, Thorsten.Kummermehr@microchip.com
Subject: Re: [PATCH net-next v4 6/6] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs
Date: Tue, 30 May 2023 11:49:16 +0200 [thread overview]
Message-ID: <0939d69afbf1173f4b62758d1d448c85217abcf1.camel@redhat.com> (raw)
In-Reply-To: <ZHRPRBwJ5jHs6vLz@debian>
On Mon, 2023-05-29 at 09:07 +0200, Ramón Nordin Rodriguez wrote:
> On Fri, May 26, 2023 at 08:53:48PM +0530, Parthiban Veerasooran wrote:
> > Add support for the Microchip LAN865x Rev.B0 10BASE-T1S Internal PHYs
> > (LAN8650/1). The LAN865x combines a Media Access Controller (MAC) and an
> > internal 10BASE-T1S Ethernet PHY to access 10BASE‑T1S networks. As
> > LAN867X and LAN865X are using the same function for the read_status,
> > rename the function as lan86xx_read_status.
> >
> > Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> > Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
> > ---
>
> I accidentally sent both reviewed-by and tested by, should only have
> been reviewed-by.
N.P. I'll strip your tested-by tag from this patch when I'll apply it.
Cheers,
Paolo
next prev parent reply other threads:[~2023-05-30 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 15:23 [PATCH net-next v4 0/6] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2023-05-26 15:23 ` [PATCH net-next v4 1/6] net: phy: microchip_t1s: modify driver description to be more generic Parthiban Veerasooran
2023-05-26 15:23 ` [PATCH net-next v4 2/6] net: phy: microchip_t1s: replace read-modify-write code with phy_modify_mmd Parthiban Veerasooran
2023-05-29 7:02 ` Ramón Nordin Rodriguez
2023-05-26 15:23 ` [PATCH net-next v4 3/6] net: phy: microchip_t1s: update LAN867x PHY supported revision number Parthiban Veerasooran
2023-05-26 15:23 ` [PATCH net-next v4 4/6] net: phy: microchip_t1s: fix reset complete status handling Parthiban Veerasooran
2023-05-29 7:04 ` Ramón Nordin Rodriguez
2023-05-26 15:23 ` [PATCH net-next v4 5/6] net: phy: microchip_t1s: remove unnecessary interrupts disabling code Parthiban Veerasooran
2023-05-26 15:23 ` [PATCH net-next v4 6/6] net: phy: microchip_t1s: add support for Microchip LAN865x Rev.B0 PHYs Parthiban Veerasooran
2023-05-29 7:06 ` Ramón Nordin Rodriguez
2023-05-29 7:07 ` Ramón Nordin Rodriguez
2023-05-30 9:49 ` Paolo Abeni [this message]
2023-05-30 10:00 ` [PATCH net-next v4 0/6] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver 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=0939d69afbf1173f4b62758d1d448c85217abcf1.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=Thorsten.Kummermehr@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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®