mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Thangaraj Samynathan <thangaraj.s@microchip.com>
Cc: bryan.whitehead@microchip.com, UNGLinuxDriver@microchip.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net 0/2] Refactor PHY reset handling and
Date: Wed, 28 May 2025 01:00:31 +0000	[thread overview]
Message-ID: <174839403100.1846337.7897415854786709434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250526053048.287095-1-thangaraj.s@microchip.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 26 May 2025 11:00:46 +0530 you wrote:
> This patch series refines the PHY reset and initialization logic in the
> lan743x driver. It includes the following changes
> 
> Rename lan743x_reset_phy to lan743x_hw_reset_phy
> Clarifies the functions purpose as performing a hardware-level PHY
> reset, improving naming consistency and readability.
> 
> [...]

Here is the summary with links:
  - [v2,net,1/2] net: lan743x: rename lan743x_reset_phy to lan743x_hw_reset_phy
    https://git.kernel.org/netdev/net/c/68927eb52d0a
  - [v2,net,2/2] net: lan743x: Fix PHY reset handling during initialization and WOL
    https://git.kernel.org/netdev/net/c/82d1096ca8b5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-05-28  0:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  5:30 Thangaraj Samynathan
2025-05-26  5:30 ` [PATCH v2 net 1/2] net: lan743x: rename lan743x_reset_phy to lan743x_hw_reset_phy Thangaraj Samynathan
2025-05-26  5:30 ` [PATCH v2 net 2/2] net: lan743x: Fix PHY reset handling during initialization and WOL Thangaraj Samynathan
2025-05-28  1:00 ` patchwork-bot+netdevbpf [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=174839403100.1846337.7897415854786709434.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thangaraj.s@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
all inboxes | Powered by JetHome®