From: patchwork-bot+netdevbpf@kernel.org
To: Yao Zi <ziyao@disroot.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, si.yanteng@linux.dev,
chenhuacai@kernel.org, rmk+kernel@armlinux.org.uk,
phasta@kernel.org, yangtiezhu@loongson.cn,
zhaoqunqin@loongson.cn, vladimir.oltean@nxp.com,
0x1207@gmail.com, hayashi.kunihiko@socionext.com,
jacob.e.keller@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jeffbai@aosc.io,
kexybiscuit@aosc.io
Subject: Re: [PATCH net-next v5 0/3] Unify platform suspend/resume routines for PCI DWMAC glue
Date: Thu, 27 Nov 2025 01:20:28 +0000 [thread overview]
Message-ID: <176420642874.1910295.6702519281405893980.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251124160417.51514-1-ziyao@disroot.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Nov 2025 16:04:14 +0000 you wrote:
> There are currently three PCI-based DWMAC glue drivers in tree,
> stmmac_pci.c, dwmac-intel.c, and dwmac-loongson.c. Both stmmac_pci.c and
> dwmac-intel.c implements the same and duplicated platform suspend/resume
> routines.
>
> This series introduces a new PCI helper library, stmmac_libpci.c,
> providing a pair of helpers, stmmac_pci_plat_{suspend,resume}, and
> replaces the driver-specific implementation with the helpers to reduce
> code duplication. The helper will also simplify the Motorcomm DWMAC glue
> driver which I'm working on.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/3] net: stmmac: Add generic suspend/resume helper for PCI-based controllers
https://git.kernel.org/netdev/net-next/c/4440bf5f2e75
- [net-next,v5,2/3] net: stmmac: loongson: Use generic PCI suspend/resume routines
https://git.kernel.org/netdev/net-next/c/c4064af1c7e3
- [net-next,v5,3/3] net: stmmac: pci: Use generic PCI suspend/resume routines
https://git.kernel.org/netdev/net-next/c/b35e94edf229
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-11-27 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 16:04 [PATCH net-next v5 0/3] Unify platform suspend/resume routines for PCI DWMAC glue Yao Zi
2025-11-24 16:04 ` [PATCH net-next v5 1/3] net: stmmac: Add generic suspend/resume helper for PCI-based controllers Yao Zi
2025-11-25 17:15 ` Russell King (Oracle)
2025-11-26 3:10 ` Yanteng Si
2025-11-24 16:04 ` [PATCH net-next v5 2/3] net: stmmac: loongson: Use generic PCI suspend/resume routines Yao Zi
2025-11-24 16:04 ` [PATCH net-next v5 3/3] net: stmmac: pci: " Yao Zi
2025-11-27 1:20 ` 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=176420642874.1910295.6702519281405893980.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x1207@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=chenhuacai@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=jacob.e.keller@intel.com \
--cc=jeffbai@aosc.io \
--cc=kexybiscuit@aosc.io \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phasta@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=si.yanteng@linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=yangtiezhu@loongson.cn \
--cc=zhaoqunqin@loongson.cn \
--cc=ziyao@disroot.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;
as well as URLs for NNTP newsgroup(s).