From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
<netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<daniel@iogearbox.net>, <pabeni@redhat.com>,
<edumazet@kernel.org>, <horms@kernel.org>, <davem@davemloft.net>,
<shuah@kernel.org>, <hawk@kernel.org>, <john.fastabend@gmail.com>,
<sdf@fomichev.me>, <willemb@google.com>, <petrm@nvidia.com>,
<bjorn@kernel.org>, <magnus.karlsson@intel.com>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next] selftests: net: don't warn when bpftool is missing
Date: Sat, 21 Nov 2026 02:06:53 +0000 [thread overview]
Message-ID: <DN0ISKVFQRMA.2NQOCMINC8LDX@gmail.com> (raw)
In-Reply-To: <20261120180307.363312fd@kernel.org>
On Sat Nov 21, 2026 at 2:03 AM UTC, Jakub Kicinski wrote:
> On Thu, 19 Nov 2026 01:11:08 +0000 Alexei Starovoitov wrote:
>> On Wed, Nov 18, 2026 at 08:53 AM Maciej Fijalkowski <maciej.fijalkowski@intel.com> wrote:
>> > Based on the bpf-net-xsk-move tag so it can go to net-next and bpf-next
>> > through another shared branch, as Alexei asked:
>>
>> Acked-by: Alexei Starovoitov <ast@kernel.org>
>>
>> Thanks for the quick fix.
>>
>> Jakub,
>> could you make another stable branch to pull?
>
> Are you sure we need to fix this? Do we care about the bot?
> We have a similar warning for having latest version of liburing
> in drivers/net. I think it's useful to let the user know that
> they are not building all the tests.
the bot seems to yell every other day 'regression' in capital letters.
I suspect people will notice sooner or later.
If you think it's ok to just ignore it, then let's do that for now.
next prev parent reply other threads:[~2026-11-21 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 16:53 [PATCH net-next] selftests: net: don't warn when bpftool is missing Maciej Fijalkowski
2026-11-19 1:11 ` Alexei Starovoitov
2026-11-21 2:03 ` Jakub Kicinski
2026-11-21 2:06 ` Alexei Starovoitov [this message]
2026-11-21 2:15 ` 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=DN0ISKVFQRMA.2NQOCMINC8LDX@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=willemb@google.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