From: Jakub Kicinski <kuba@kernel.org>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<magnus.karlsson@intel.com>, <stfomichev@gmail.com>,
<pabeni@redhat.com>, <horms@kernel.org>,
<tushar.vyavahare@intel.com>, <kerneljasonxing@gmail.com>
Subject: Re: [PATCH net-next] selftests/xsk: preserve UMEM view in bidi test
Date: Thu, 25 Jun 2026 07:36:36 -0700 [thread overview]
Message-ID: <20260625073636.449a28c0@kernel.org> (raw)
In-Reply-To: <aj0EYNt7Sr1dD96N@boxer>
On Thu, 25 Jun 2026 12:35:12 +0200 Maciej Fijalkowski wrote:
> On Wed, Jun 24, 2026 at 07:33:26PM -0700, Jakub Kicinski wrote:
> > On Tue, 23 Jun 2026 11:10:08 +0200 Maciej Fijalkowski wrote:
> > > Subject: [PATCH net-next] selftests/xsk: preserve UMEM view in bidi test
> >
> > Do you want it in net? Either way - we'll need a rebase
>
> I have not checked if this has been -net propagated already, but the rule
> of thumb on bpf side was that all selftests related effort goes to -next.
> Is it different on netdev side?
We prefer -next too, but during the merge window net-next is closed.
What we definitely don't want is a -next patch with a Fixes tag.
So either net or drop the tag, please.
next prev parent reply other threads:[~2026-06-25 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:10 [PATCH net-next] selftests/xsk: preserve UMEM view in bidi test Maciej Fijalkowski
2026-06-24 3:47 ` Vyavahare, Tushar
2026-06-25 2:33 ` Jakub Kicinski
2026-06-25 10:35 ` Maciej Fijalkowski
2026-06-25 14:36 ` Jakub Kicinski [this message]
2026-06-25 15:21 ` Maciej Fijalkowski
2026-06-25 15:29 ` Jakub Kicinski
2026-06-25 13:38 ` Jason Xing
2026-06-25 14:47 ` Jakub Sitnicki
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=20260625073636.449a28c0@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.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.