From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Daniel Borkmann <daniel@iogearbox.net>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v3 bpf-next] selftests/bpf: Replace %pK output with 0
Date: Thu, 24 Sep 2026 19:33:07 +0200 [thread overview]
Message-ID: <20260924173307.FQgZQfVP@linutronix.de> (raw)
In-Reply-To: <DLNO7GO4QMNE.23673O3BC9B7@gmail.com>
On 2026-09-24 16:00:47 [+0000], Alexei Starovoitov wrote:
> On Thu, Sep 24, 2026 at 05:31 PM Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> > v2…v3: https://lore.kernel.org/all/20260918102610.gxA3km8_@linutronix.de/
> > - correct the subject line
> > - correct grammar error in the commit description
> > - Pickup a reviewed-by tag from Emil which was sent for v1
>
> v2 was applied to bpf-next two days ago.
> See commit 79dc258c9392 ("selftests/bpf: Replace %pK output with 0").
> The code in v3 is the same. Nothing to apply.
Oh, thank you. I haven't seen a mail from the bot and the patch tracker
said had "changes requested".
Sebastian
next prev parent reply other threads:[~2026-09-24 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 15:31 [PATCH v3 bpf-next] selftests/bpf: Replace %pK output with 0 Sebastian Andrzej Siewior
2026-09-24 16:00 ` Alexei Starovoitov
2026-09-24 17:33 ` Sebastian Andrzej Siewior [this message]
2026-09-24 16:03 ` Daniel Borkmann
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=20260924173307.FQgZQfVP@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox