Netdev List
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Megane Hebo <hebomegane@gmail.com>,  netdev@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org,  davem@davemloft.net,
	 edumazet@kernel.org,  kuba@kernel.org,  pabeni@redhat.com,
	 horms@kernel.org,  shuah@kernel.org,  mst@redhat.com,
	 virtualization@lists.linux.dev,
	 willemdebruijn.kernel@gmail.com,  habte.yibelo@gmail.com,
	 jasowangio@gmail.com,  eperezma@redhat.com,
	 xuanzhuo@linux.alibaba.com
Subject: Re: [RFC PATCH net-next] selftests: net: exercise virtio checksum ingress outcomes
Date: Sat, 17 Oct 2026 11:55:26 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.eb0f6ff37e8f@gmail.com> (raw)
In-Reply-To: <CAJPVW+nstfbagm9GxQ=i-5J6Xi_aZ52-YiQZeYrzmPD3OmDNiw@mail.gmail.com>

Megane Hebo wrote:
> Correction: Gmail Web rewrote tabs and wrapped some long lines in the
> inline diff I just sent, so that copy is not suitable for applying.
> 
> The attached format-patch file is the authoritative byte-exact patch.
> Sorry for the transport noise.
> 
> SHA256: cd11c3970f0a23ac039cdfcdc6338c20c79dbff3db8fdc93ea53b4b8996437b8

This is not the way to send patches

https://docs.kernel.org/process/submitting-patches.html

More in-depth: with AI it is easy to generate testcases. We now have
to consider which ones are important enough to submit. I think we all
have reproducers for these specific fixes offline. If we had thought
it worthwhile they would have been included in the feature series
itself.


  reply	other threads:[~2026-10-17 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17  6:00 [RFC PATCH net-next] selftests: net: exercise virtio checksum ingress outcomes Megane Hebo
2026-10-17  6:02 ` Megane Hebo
2026-10-17 15:55   ` Willem de Bruijn [this message]
2026-10-17 16:35     ` Megane Hebo

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=willemdebruijn.kernel.eb0f6ff37e8f@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=habte.yibelo@gmail.com \
    --cc=hebomegane@gmail.com \
    --cc=horms@kernel.org \
    --cc=jasowangio@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --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