From: patchwork-bot+netdevbpf@kernel.org
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
virtualization@lists.linux-foundation.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] virtio-net: fix for build_skb()
Date: Thu, 13 May 2021 23:00:11 +0000 [thread overview]
Message-ID: <162094681137.5074.5504584757048483865.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210513114808.120031-1-xuanzhuo@linux.alibaba.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 13 May 2021 19:48:06 +0800 you wrote:
> #1 Fixed a serious error.
> #2 Fixed a logical error, but this error did not cause any serious consequences.
>
> The logic of this piece is really messy. Fortunately, my refactored patch can be
> completed with a small amount of testing.
>
> Thanks.
>
> [...]
Here is the summary with links:
- [net-next,1/2] virtio-net: fix for unable to handle page fault for address
https://git.kernel.org/netdev/net-next/c/6c66c147b9a4
- [net-next,2/2] virtio-net: get build_skb() buf by data ptr
https://git.kernel.org/netdev/net-next/c/7bf64460e3b2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-05-13 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 11:48 [PATCH net-next 0/2] virtio-net: fix for build_skb() Xuan Zhuo
2021-05-13 11:48 ` [PATCH net-next 1/2] virtio-net: fix for unable to handle page fault for address Xuan Zhuo
2021-05-13 11:48 ` [PATCH net-next 2/2] virtio-net: get build_skb() buf by data ptr Xuan Zhuo
2021-05-13 23:00 ` patchwork-bot+netdevbpf [this message]
2021-05-14 14:04 ` [PATCH net-next 0/2] virtio-net: fix for build_skb() Michael S. Tsirkin
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=162094681137.5074.5504584757048483865.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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