From: patchwork-bot+netdevbpf@kernel.org
To: Kevin Hao <haokexin@gmail.com>
Cc: netdev@vger.kernel.org, nicolas.ferre@microchip.com,
claudiu.beznea@tuxon.dev, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, quanyang.wang@windriver.com,
stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: macb: Fix Ethernet malfunction on AMD Versal board after suspend
Date: Sat, 14 Mar 2026 19:30:07 +0000 [thread overview]
Message-ID: <177351660779.1763199.11769087375422491221.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260312-macb-versal-v1-0-467647173fa4@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Mar 2026 16:13:57 +0800 you wrote:
> Hi,
>
> On Versal boards, the tx/rx queue pointer registers are cleared after suspend,
> which causes Ethernet malfunction. This patch series addresses this issue by
> reinitializing the tx/rx queue pointer registers and the rx ring.
>
>
> [...]
Here is the summary with links:
- [net,1/2] net: macb: Introduce gem_init_rx_ring()
https://git.kernel.org/netdev/net/c/1a7124ecd655
- [net,2/2] net: macb: Reinitialize tx/rx queue pointer registers and rx ring during resume
https://git.kernel.org/netdev/net/c/718d0766ce4c
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:[~2026-03-14 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:13 [PATCH net 0/2] net: macb: Fix Ethernet malfunction on AMD Versal board after suspend Kevin Hao
2026-03-12 8:13 ` [PATCH net 1/2] net: macb: Introduce gem_init_rx_ring() Kevin Hao
2026-03-12 8:13 ` [PATCH net 2/2] net: macb: Reinitialize tx/rx queue pointer registers and rx ring during resume Kevin Hao
2026-03-13 14:12 ` [PATCH net 0/2] net: macb: Fix Ethernet malfunction on AMD Versal board after suspend Simon Horman
2026-03-14 19: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=177351660779.1763199.11769087375422491221.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haokexin@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=quanyang.wang@windriver.com \
--cc=stable@vger.kernel.org \
/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