Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hayes Wang <hayeswang@realtek.com>
Cc: hkallweit1@gmail.com, netdev@vger.kernel.org,
nic_swsd@realtek.com, koba.ko@canonical.com
Subject: Re: [PATCH net-next 0/2] r8169: adjust the setting for RTL8106e
Date: Sat, 07 Aug 2021 08:40:05 +0000 [thread overview]
Message-ID: <162832560583.30769.1619629490600315704.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210806091556.1297186-374-nic_swsd@realtek.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Fri, 6 Aug 2021 17:15:54 +0800 you wrote:
> These patches are uesed to avoid the delay of link-up interrupt, when
> enabling ASPM for RTL8106e. The patch #1 is used to enable ASPM if
> it is possible. And the patch #2 is used to modify the entrance latencies
> of L0 and L1.
>
> Hayes Wang (2):
> Revert "r8169: avoid link-up interrupt issue on RTL8106e if user
> enables ASPM"
> r8169: change the L0/L1 entrance latencies for RTL8106e
>
> [...]
Here is the summary with links:
- [net-next,1/2] Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM"
https://git.kernel.org/netdev/net/c/2115d3d48265
- [net-next,2/2] r8169: change the L0/L1 entrance latencies for RTL8106e
https://git.kernel.org/netdev/net/c/9c4018648814
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:[~2021-08-07 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 9:15 [PATCH net-next 0/2] r8169: adjust the setting for RTL8106e Hayes Wang
2021-08-06 9:15 ` [PATCH net-next 1/2] Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" Hayes Wang
2021-08-06 9:15 ` [PATCH net-next 2/2] r8169: change the L0/L1 entrance latencies for RTL8106e Hayes Wang
2021-08-06 21:27 ` Heiner Kallweit
2021-08-07 3:50 ` Hayes Wang
2021-08-07 8: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=162832560583.30769.1619629490600315704.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=hayeswang@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=koba.ko@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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;
as well as URLs for NNTP newsgroup(s).