From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
Tushar Vyavahare <tushar.vyavahare@intel.com>,
<netdev@vger.kernel.org>, <magnus.karlsson@intel.com>,
<stfomichev@gmail.com>, <kernelxing@tencent.com>,
<davem@davemloft.net>, <ast@kernel.org>, <daniel@iogearbox.net>,
<tirthendu.sarkar@intel.com>, <andrii@kernel.org>,
<bpf@vger.kernel.org>
Subject: Re: [PATCH net-next v3 0/4] selftests/xsk: improve shared-UMEM coverage
Date: Thu, 20 Aug 2026 19:53:00 +0200 [thread overview]
Message-ID: <aoc+/OW8Gy4ZOx+w@boxer> (raw)
In-Reply-To: <20260820104419.050cbc44@kernel.org>
On Thu, Aug 20, 2026 at 10:44:19AM -0700, Jakub Kicinski wrote:
> On Thu, 20 Aug 2026 11:35:53 +0200 Paolo Abeni wrote:
> > ## Form letter - net-next-closed
>
> these are bpf patches. Tushar, tools/testing/selftests/bpf is BPF
But AF_XDP is now net target since some time. Should we move the test
suite out of bpf directory then?
next prev parent reply other threads:[~2026-08-20 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 2:44 [PATCH net-next v3 0/4] selftests/xsk: improve shared-UMEM coverage Tushar Vyavahare
2026-08-19 2:44 ` [PATCH net-next v3 1/4] selftests/xsk: add UMEM users refcount and centralize socket teardown Tushar Vyavahare
2026-08-20 2:47 ` sashiko-bot
2026-08-20 18:42 ` bot+bpf-ci
2026-08-19 2:44 ` [PATCH net-next v3 2/4] selftests/xsk: skip TX setup after RX configuration failure Tushar Vyavahare
2026-08-20 18:27 ` bot+bpf-ci
2026-08-19 2:44 ` [PATCH net-next v3 3/4] selftests/xsk: expand XSKMAP capacity and add length-based XDP program Tushar Vyavahare
2026-08-19 2:44 ` [PATCH net-next v3 4/4] selftests/xsk: add shared-UMEM callback framework and initial test cases Tushar Vyavahare
2026-08-20 18:42 ` bot+bpf-ci
2026-08-20 9:35 ` [PATCH net-next v3 0/4] selftests/xsk: improve shared-UMEM coverage Paolo Abeni
2026-08-20 17:44 ` Jakub Kicinski
2026-08-20 17:53 ` Maciej Fijalkowski [this message]
2026-08-20 21:29 ` Jakub Kicinski
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=aoc+/OW8Gy4ZOx+w@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=tirthendu.sarkar@intel.com \
--cc=tushar.vyavahare@intel.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.