From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: pabeni@redhat.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, nic_swsd@realtek.com,
netdev@vger.kernel.org, simon.horman@corigine.com,
kai.heng.feng@canonical.com, holger@applied-asynchrony.com
Subject: Re: [PATCH net-next 0/6] r8169: disable ASPM during NAPI poll
Date: Wed, 08 Mar 2023 10:00:20 +0000 [thread overview]
Message-ID: <167826962073.12133.6381622389271772014.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b434a0ce-9a76-e227-3267-ee26497ec446@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 6 Mar 2023 22:17:28 +0100 you wrote:
> This is a rework of ideas from Kai-Heng on how to avoid the known
> ASPM issues whilst still allowing for a maximum of ASPM-related power
> savings. As a prerequisite some locking is added first.
>
> Heiner Kallweit (6):
> r8169: use spinlock to protect mac ocp register access
> r8169: use spinlock to protect access to registers Config2 and Config5
> r8169: enable cfg9346 config register access in atomic context
> r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context
> r8169: disable ASPM during NAPI poll
> r8169: remove ASPM restrictions now that ASPM is disabled during NAPI
> poll
>
> [...]
Here is the summary with links:
- [net-next,1/6] r8169: use spinlock to protect mac ocp register access
https://git.kernel.org/netdev/net-next/c/91c8643578a2
- [net-next,2/6] r8169: use spinlock to protect access to registers Config2 and Config5
https://git.kernel.org/netdev/net-next/c/6bc6c4e6893e
- [net-next,3/6] r8169: enable cfg9346 config register access in atomic context
https://git.kernel.org/netdev/net-next/c/59ee97c0c1a8
- [net-next,4/6] r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context
https://git.kernel.org/netdev/net-next/c/49ef7d846d4b
- [net-next,5/6] r8169: disable ASPM during NAPI poll
https://git.kernel.org/netdev/net-next/c/e1ed3e4d9111
- [net-next,6/6] r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll
https://git.kernel.org/netdev/net-next/c/2ab19de62d67
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:[~2023-03-08 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 21:17 [PATCH net-next 0/6] r8169: disable ASPM during NAPI poll Heiner Kallweit
2023-03-06 21:23 ` [PATCH net-next 1/6] r8169: use spinlock to protect mac ocp register access Heiner Kallweit
2023-03-06 21:24 ` [PATCH net-next 2/6] r8169: use spinlock to protect access to registers Config2 and Config5 Heiner Kallweit
2023-03-06 21:24 ` [PATCH net-next 3/6] r8169: enable cfg9346 config register access in atomic context Heiner Kallweit
2023-03-06 21:25 ` [PATCH net-next 4/6] r8169: prepare rtl_hw_aspm_clkreq_enable for usage " Heiner Kallweit
2023-03-06 21:26 ` [PATCH net-next 5/6] r8169: disable ASPM during NAPI poll Heiner Kallweit
2023-03-06 21:28 ` [PATCH net-next 6/6] r8169: remove ASPM restrictions now that ASPM is disabled " Heiner Kallweit
2023-03-08 10: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=167826962073.12133.6381622389271772014.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=holger@applied-asynchrony.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.