From: Sasha Levin <sashal@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
gregkh@linuxfoundation.org
Cc: "Sasha Levin" <sashal@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
"Ricardo B. Marlière (SUSE)" <ricardo@marliere.net>,
"Michal Luczaj" <mhal@rbox.co>,
"Kuniyuki Iwashima" <kuniyu@google.com>,
"Jakub Sitnicki" <jakub@cloudflare.com>
Subject: Re: [PATCH 7.1.y v2 0/2] selftests: Fixes for BPF
Date: Sun, 16 Aug 2026 23:25:13 -0400 [thread overview]
Message-ID: <20260816211000.7@kernel.org> (raw)
In-Reply-To: <20260815-7-1-y-selftests-bpf-udp_xsk-v2-0-c227473a2300@marliere.net>
> Please consider merging the following patches, found through openSUSE CI,
> for test_progs (subtests sockmap_basic and sockmap_listen):
>
> Changes in v2:
> - Corrected upstream refs
Queued the series for 7.1, thanks.
The kernel-side change these tests follow is released on the older trees too,
so I picked the same fixes up for 6.18, 6.12, 6.6 and 6.1 as well - 6.6 and
6.1 only needed the sockmap update error handling change, and 6.1 also needed
the test_maps.c counterpart.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-17 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 12:50 [PATCH 7.1.y v2 0/2] selftests: Fixes for BPF Ricardo B. Marlière (SUSE)
2026-08-15 12:50 ` [PATCH 7.1.y v2 1/2] selftests/bpf: Ensure UDP sockets are bound Ricardo B. Marlière (SUSE)
2026-08-15 12:50 ` [PATCH 7.1.y v2 2/2] selftests/bpf: Adapt sockmap update error handling Ricardo B. Marlière (SUSE)
2026-08-17 3:25 ` Sasha Levin [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=20260816211000.7@kernel.org \
--to=sashal@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jakub@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mhal@rbox.co \
--cc=ricardo@marliere.net \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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.