All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Xu Du <xudu@redhat.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org, shuah@kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/8] selftest: Extend tun/virtio coverage for GSO over UDP tunnel
Date: Mon, 5 Jan 2026 17:36:24 -0800	[thread overview]
Message-ID: <20260105173624.43fe986b@kernel.org> (raw)
In-Reply-To: <cover.1767580224.git.xudu@redhat.com>

On Mon,  5 Jan 2026 11:44:35 +0800 Xu Du wrote:
> v2 -> v3:
>  - Re-send the patch series becasue Patchwork don't update them

Not sure what this means, but:
 1 - please do not repost patches sooner than 24h after previous
     posting, per
     https://www.kernel.org/doc/html/next/process/maintainer-netdev.html

 2 - the patches do not apply to net-next:

Applying: selftest: tun: Format tun.c existing code
Applying: selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing
Applying: selftest: tun: Refactor tun_delete to use tuntap_helpers
Applying: selftest: tap: Refactor tap test to use tuntap_helpers
Using index info to reconstruct a base tree...
M	tools/testing/selftests/net/tap.c
Falling back to patching base and 3-way merge...
Auto-merging tools/testing/selftests/net/tap.c
CONFLICT (content): Merge conflict in tools/testing/selftests/net/tap.c
Recorded preimage for 'tools/testing/selftests/net/tap.c'
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0004 selftest: tap: Refactor tap test to use tuntap_helpers

      parent reply	other threads:[~2026-01-06  1:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  3:44 [PATCH net-next v3 0/8] selftest: Extend tun/virtio coverage for GSO over UDP tunnel Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 1/8] selftest: tun: Format tun.c existing code Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 2/8] selftest: tun: Introduce tuntap_helpers.h header for TUN/TAP testing Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 3/8] selftest: tun: Refactor tun_delete to use tuntap_helpers Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 4/8] selftest: tap: Refactor tap test " Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 5/8] selftest: tun: Add helpers for GSO over UDP tunnel Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 6/8] selftest: tun: Add test for sending gso packet into tun Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 7/8] selftest: tun: Add test for receiving gso packet from tun Xu Du
2026-01-05  3:44 ` [PATCH net-next v3 8/8] selftest: tun: Add test data for success and failure paths Xu Du
2026-01-06  1:36 ` Jakub Kicinski [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=20260105173624.43fe986b@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=xudu@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 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.