From: patchwork-bot+netdevbpf@kernel.org
To: ChunHao Lin <hau@realtek.com>
Cc: hkallweit1@gmail.com, nic_swsd@realtek.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4 0/2] r8169: fix DASH devices network lost issue
Date: Tue, 14 Nov 2023 05:10:25 +0000 [thread overview]
Message-ID: <169993862517.6042.11181056876450979289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231109173400.4573-1-hau@realtek.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 Nov 2023 01:33:58 +0800 you wrote:
> This series are used to fix network lost issue on systems that support
> DASH. It has been tested on rtl8168ep and rtl8168fp.
>
>
> V3 -> V4: Fix a coding style issue.
> V2 -> V3: Add 'Fixes' tag and correct indentation.
> V1 -> V2: Change variable and function name. And update DASH info message.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] r8169: add handling DASH when DASH is disabled
https://git.kernel.org/netdev/net/c/0ab0c45d8aae
- [net,v4,2/2] r8169: fix network lost after resume on DASH systems
https://git.kernel.org/netdev/net/c/868c3b95afef
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-11-14 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 17:33 [PATCH net v4 0/2] r8169: fix DASH devices network lost issue ChunHao Lin
2023-11-09 17:33 ` [PATCH net v4 1/2] r8169: add handling DASH when DASH is disabled ChunHao Lin
2023-11-09 17:39 ` Heiner Kallweit
2023-11-09 17:34 ` [PATCH net v4 2/2] r8169: fix network lost after resume on DASH systems ChunHao Lin
2023-11-14 5:10 ` 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=169993862517.6042.11181056876450979289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hau@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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