netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, lxu@maxlinear.com,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	bryan.whitehead@microchip.com, richardcochran@gmail.com,
	UNGLinuxDriver@microchip.com, Ian.Saturley@microchip.com
Subject: Re: [PATCH net-next V2 3/4] net: lan743x: Add support to SGMII 1G and 2.5G
Date: Thu, 16 Jun 2022 21:17:49 +0200	[thread overview]
Message-ID: <YquB3dl7mWXvKn9V@lunn.ch> (raw)
In-Reply-To: <20220616041226.26996-4-Raju.Lakkaraju@microchip.com>

On Thu, Jun 16, 2022 at 09:42:25AM +0530, Raju Lakkaraju wrote:
> Add SGMII access read and write functions
> Add support to SGMII 1G and 2.5G for PCI11010/PCI11414 chips
> 
> Signed-off-by: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  

  reply	other threads:[~2022-06-16 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  4:12 [PATCH net-next V2 0/4] net: lan743x: PCI11010 / PCI11414 devices Enhancements Raju Lakkaraju
2022-06-16  4:12 ` [PATCH net-next V2 1/4] net: lan743x: Add support to LAN743x register dump Raju Lakkaraju
2022-06-16 19:11   ` Andrew Lunn
2022-06-16  4:12 ` [PATCH net-next V2 2/4] net: lan743x: Add support to Secure-ON WOL Raju Lakkaraju
2022-06-16 19:13   ` Andrew Lunn
2022-06-16  4:12 ` [PATCH net-next V2 3/4] net: lan743x: Add support to SGMII 1G and 2.5G Raju Lakkaraju
2022-06-16 19:17   ` Andrew Lunn [this message]
2022-06-16  4:12 ` [PATCH net-next V2 4/4] net: phy: add support to get Master-Slave configuration Raju Lakkaraju
2022-06-16 19:18   ` Andrew Lunn
2022-06-17  3:50 ` [PATCH net-next V2 0/4] net: lan743x: PCI11010 / PCI11414 devices Enhancements 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=YquB3dl7mWXvKn9V@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Ian.Saturley@microchip.com \
    --cc=Raju.Lakkaraju@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lxu@maxlinear.com \
    --cc=netdev@vger.kernel.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).