From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
horms@kernel.org, hkallweit1@gmail.com, richardcochran@gmail.com,
rdunlap@infradead.org, linux@armlinux.org.uk,
bryan.whitehead@microchip.com, edumazet@google.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next V2 2/4] net: lan743x: Create separate Link Speed Duplex state function
Date: Thu, 18 Jul 2024 05:33:37 +0200 [thread overview]
Message-ID: <57198c26-7585-4829-b267-059d0e7e548c@lunn.ch> (raw)
In-Reply-To: <20240716113349.25527-3-Raju.Lakkaraju@microchip.com>
On Tue, Jul 16, 2024 at 05:03:47PM +0530, Raju Lakkaraju wrote:
> Create separate Link Speed Duplex (LSD) update state function from
> lan743x_sgmii_config () to use as subroutine.
>
> Signed-off-by: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-07-18 3:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 11:33 [PATCH net-next V2 0/4] Add support to PHYLINK for LAN743x/PCI11x1x chips Raju Lakkaraju
2024-07-16 11:33 ` [PATCH net-next V2 1/4] net: lan743x: Create separate PCS power reset function Raju Lakkaraju
2024-07-18 3:30 ` Andrew Lunn
2024-07-16 11:33 ` [PATCH net-next V2 2/4] net: lan743x: Create separate Link Speed Duplex state function Raju Lakkaraju
2024-07-18 3:33 ` Andrew Lunn [this message]
2024-07-16 11:33 ` [PATCH net-next V2 3/4] net: lan743x: Migrate phylib to phylink Raju Lakkaraju
2024-07-18 3:43 ` Andrew Lunn
2024-07-25 9:34 ` Raju Lakkaraju
2024-07-29 9:16 ` Russell King (Oracle)
2024-07-30 10:48 ` Raju Lakkaraju
2024-07-30 11:29 ` Russell King (Oracle)
2024-07-16 11:33 ` [PATCH net-next V2 4/4] net: lan743x: Add support to ethtool phylink get and set settings Raju Lakkaraju
2024-07-16 13:17 ` [PATCH net-next V2 0/4] Add support to PHYLINK for LAN743x/PCI11x1x chips Paolo Abeni
2024-07-16 13:37 ` Jiri Pirko
2024-07-18 3:27 ` Andrew Lunn
2024-07-18 5:08 ` Raju Lakkaraju
2024-07-18 15:09 ` Andrew Lunn
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=57198c26-7585-4829-b267-059d0e7e548c@lunn.ch \
--to=andrew@lunn.ch \
--cc=Raju.Lakkaraju@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richardcochran@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;
as well as URLs for NNTP newsgroup(s).