virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
	thuth@linux.vnet.ibm.com, jasowang@redhat.com, mst@redhat.com,
	xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com
Subject: Re: [PATCH 0/2] virtio_net: fixes for checksum offloading and XDP handling
Date: Wed, 19 Jun 2024 10:00:31 +0000	[thread overview]
Message-ID: <171879123138.351.9134689741507431412.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240617131524.63662-1-hengqi@linux.alibaba.com>

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon, 17 Jun 2024 21:15:22 +0800 you wrote:
> This series of patches aim to address two specific issues identified in
> the virtio_net driver related to checksum offloading and XDP processing of
> fully checksummed packets.
> 
> The first patch corrects the handling of checksum offloading in the driver.
> The second patch addresses an issue where the XDP program had no trouble
> with fully checksummed packets.
> 
> [...]

Here is the summary with links:
  - [1/2] virtio_net: checksum offloading handling fix
    https://git.kernel.org/netdev/net/c/604141c036e1
  - [2/2] virtio_net: fixing XDP for fully checksummed packets handling
    https://git.kernel.org/netdev/net/c/703eec1b2422

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-19 10:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 13:15 [PATCH 0/2] virtio_net: fixes for checksum offloading and XDP handling Heng Qi
2024-06-17 13:15 ` [PATCH 1/2] virtio_net: checksum offloading handling fix Heng Qi
2024-06-17 13:34   ` Jiri Pirko
2024-06-18  3:01   ` Jason Wang
2024-06-18  3:09     ` Heng Qi
2024-06-19  1:15       ` Jakub Kicinski
2024-06-19  2:02         ` Heng Qi
2024-06-19 15:08           ` Jakub Kicinski
2024-06-19 15:44             ` Heng Qi
2024-06-20  8:29               ` Jason Wang
2024-06-17 13:15 ` [PATCH 2/2] virtio_net: fixing XDP for fully checksummed packets handling Heng Qi
2024-06-18  3:10   ` Jason Wang
2024-06-18  3:15     ` Heng Qi
2024-06-20  8:33       ` Jason Wang
2024-06-20  9:28         ` Heng Qi
2024-06-20 10:19           ` Michael S. Tsirkin
2024-06-20 10:27             ` Heng Qi
2024-06-20 10:38               ` Heng Qi
2024-06-20 10:45                 ` Michael S. Tsirkin
2024-06-19 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=171879123138.351.9134689741507431412.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=hawk@kernel.org \
    --cc=hengqi@linux.alibaba.com \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thuth@linux.vnet.ibm.com \
    --cc=virtualization@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).