netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Rengarajan S <rengarajan.s@microchip.com>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] lan78xx: Enable 125 MHz CLK and Auto Speed configuration for LAN7801 if NO EEPROM is detected
Date: Wed, 15 May 2024 17:22:31 +0100	[thread overview]
Message-ID: <20240515162231.GA179178@kernel.org> (raw)
In-Reply-To: <20240514160201.1651627-1-rengarajan.s@microchip.com>

On Tue, May 14, 2024 at 09:31:59PM +0530, Rengarajan S wrote:
> This patch series adds the support for 125 MHz clock, Auto speed and
> auto duplex configuration for LAN7801 in the absence of EEPROM.
> 
> Rengarajan S (2):
>   lan78xx: Enable 125 MHz CLK configuration for LAN7801 if NO EEPROM is
>     detected
>   lan78xx: Enable Auto Speed and Auto Duplex configuration for LAN7801
>     if NO EEPROM is detected
> 
> v2
> Split the patches into 125 MHz clock support and Auto speed config
> support for LAN7801.
> v1
> Initial Commit.

Hi Rengarajan,

Thanks for the revised patches, they look good to me.

Unfortunately, net-next is currently closed for the v6.10 merge window.
Please consider reposting once net-next re-opens, after 27th May.

Also, feel free to include:

Reviewed-by: Simon Horman <horms@kernel.org>

-- 
pw-bot: defer



      parent reply	other threads:[~2024-05-15 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 16:01 [PATCH net-next v2 0/2] lan78xx: Enable 125 MHz CLK and Auto Speed configuration for LAN7801 if NO EEPROM is detected Rengarajan S
2024-05-14 16:02 ` [PATCH net-next v2 1/2] lan78xx: Enable 125 MHz CLK " Rengarajan S
2024-05-14 16:02 ` [PATCH net-next v2 2/2] lan78xx: Enable Auto Speed and Auto Duplex " Rengarajan S
2024-05-15 16:22 ` Simon Horman [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=20240515162231.GA179178@kernel.org \
    --to=horms@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rengarajan.s@microchip.com \
    --cc=woojung.huh@microchip.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).