From: patchwork-bot+netdevbpf@kernel.org
To: Chunhao Lin <hau@realtek.com>
Cc: hkallweit1@gmail.com, netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: [PATCH net v3 0/2] fix dmar pte write access is not set error
Date: Wed, 28 Dec 2022 12:00:16 +0000 [thread overview]
Message-ID: <167222881688.20935.5501049497552622674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221226123153.4406-1-hau@realtek.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 26 Dec 2022 20:31:51 +0800 you wrote:
> This series fixes dmar pte write access is not set error.
>
> Chunhao Lin (2):
> r8169: move rtl_wol_enable_rx() and rtl_prepare_power_down()
> r8169: fix dmar pte write access is not set error
>
> v2:
> -update commit message
> -adjust the code according to current kernel code
> v3:
> -update title and commit message
> -split the patch
>
> [...]
Here is the summary with links:
- [net,v3,1/2] r8169: move rtl_wol_enable_rx() and rtl_prepare_power_down()
https://git.kernel.org/netdev/net/c/ad425666a1f0
- [net,v3,2/2] r8169: fix dmar pte write access is not set error
https://git.kernel.org/netdev/net/c/bb41c13c05c2
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:[~2022-12-28 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 12:31 [PATCH net v3 0/2] fix dmar pte write access is not set error Chunhao Lin
2022-12-26 12:31 ` [PATCH net v3 1/2] r8169: move rtl_wol_enable_rx() and rtl_prepare_power_down() Chunhao Lin
2022-12-26 12:47 ` Heiner Kallweit
2022-12-26 12:31 ` [PATCH net v3 2/2] r8169: fix dmar pte write access is not set error Chunhao Lin
2022-12-26 12:47 ` Heiner Kallweit
2022-12-28 12: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=167222881688.20935.5501049497552622674.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=hau@realtek.com \
--cc=hkallweit1@gmail.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 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.