The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Klein <michael@fossekall.de>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [net-next v7 0/6] net: phy: realtek: Add support for PHY LEDs
Date: Tue, 06 May 2025 11:40:33 +0000	[thread overview]
Message-ID: <174653163399.1488563.15219009456248413531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250504172916.243185-1-michael@fossekall.de>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sun,  4 May 2025 19:29:10 +0200 you wrote:
> Changes in V7:
> - Remove some unused macros (patch 1)
> - Add more register defines for RTL8211F (patch 3)
> - Revise macro definition order once more (patch 4)
> 
> Changes in V6:
> - fix macro definition order (patch 1)
> - introduce two more register defines (patch 2)
> 
> [...]

Here is the summary with links:
  - [net-next,v7,1/6] net: phy: realtek: remove unsed RTL821x_PHYSR* macros
    https://git.kernel.org/netdev/net-next/c/f3b265358b91
  - [net-next,v7,2/6] net: phy: realtek: Clean up RTL821x ExtPage access
    https://git.kernel.org/netdev/net-next/c/7c6fa3ffd265
  - [net-next,v7,3/6] net: phy: realtek: add RTL8211F register defines
    https://git.kernel.org/netdev/net-next/c/12d40df259e3
  - [net-next,v7,4/6] net: phy: realtek: Group RTL82* macro definitions
    https://git.kernel.org/netdev/net-next/c/8c4d0172657c
  - [net-next,v7,5/6] net: phy: realtek: use __set_bit() in rtl8211f_led_hw_control_get()
    https://git.kernel.org/netdev/net-next/c/be1cc96ddf82
  - [net-next,v7,6/6] net: phy: realtek: Add support for PHY LEDs on RTL8211E
    https://git.kernel.org/netdev/net-next/c/708686132ba0

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-06 11:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 17:29 [net-next v7 0/6] net: phy: realtek: Add support for PHY LEDs Michael Klein
2025-05-04 17:29 ` [net-next v7 1/6] net: phy: realtek: remove unsed RTL821x_PHYSR* macros Michael Klein
2025-05-04 17:29 ` [net-next v7 2/6] net: phy: realtek: Clean up RTL821x ExtPage access Michael Klein
2025-05-05 22:05   ` Andrew Lunn
2025-05-04 17:29 ` [net-next v7 3/6] net: phy: realtek: add RTL8211F register defines Michael Klein
2025-05-05 22:06   ` Andrew Lunn
2025-05-04 17:29 ` [net-next v7 4/6] net: phy: realtek: Group RTL82* macro definitions Michael Klein
2025-05-05 22:09   ` Andrew Lunn
2025-05-04 17:29 ` [net-next v7 5/6] net: phy: realtek: use __set_bit() in rtl8211f_led_hw_control_get() Michael Klein
2025-05-04 17:29 ` [net-next v7 6/6] net: phy: realtek: Add support for PHY LEDs on RTL8211E Michael Klein
2025-05-06 11:40 ` 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=174653163399.1488563.15219009456248413531.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@fossekall.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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