From: patchwork-bot+netdevbpf@kernel.org
To: Kyle Hendry <kylehendrydev@gmail.com>
Cc: florian.fainelli@broadcom.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, noltari@gmail.com, jonas.gorski@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND net-next 0/2] net: dsa: b53: mmap: Add bcm63268 GPHY power control
Date: Fri, 15 Aug 2025 01:30:16 +0000 [thread overview]
Message-ID: <175522141623.510661.3222510491838583574.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250814002530.5866-1-kylehendrydev@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 Aug 2025 17:25:26 -0700 you wrote:
> The gpio controller on the bcm63268 has a register for
> controlling the gigabit phy power. These patches disable
> low power mode when enabling the gphy port.
>
> This is based on an earlier patch series here:
> https://lore.kernel.org/netdev/20250306053105.41677-1-kylehendrydev@gmail.com/
>
> [...]
Here is the summary with links:
- [RESEND,net-next,1/2] net: dsa: b53: mmap: Add gphy port to phy info for bcm63268
https://git.kernel.org/netdev/net-next/c/7f95f04fe190
- [RESEND,net-next,2/2] net: dsa: b53: mmap: Implement bcm63268 gphy power control
https://git.kernel.org/netdev/net-next/c/61730ac10ba9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-15 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 0:25 Kyle Hendry
2025-08-14 0:25 ` [PATCH RESEND net-next 1/2] net: dsa: b53: mmap: Add gphy port to phy info for bcm63268 Kyle Hendry
2025-08-14 0:25 ` [PATCH RESEND net-next 2/2] net: dsa: b53: mmap: Implement bcm63268 gphy power control Kyle Hendry
2025-08-15 1:30 ` 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=175522141623.510661.3222510491838583574.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=kylehendrydev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--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
all inboxes | Powered by JetHome®