From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Christopher Hoy Poy <choypoy@linuxfoundation.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
patchwork-bot+netdevbpf@kernel.org,
Ilya Leoshkevich <iii@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock
Date: Fri, 25 Apr 2025 09:25:51 -0700 [thread overview]
Message-ID: <20250425092551.2891651d@kernel.org> (raw)
In-Reply-To: <20250424-imported-beautiful-orangutan-bb09e0@meerkat>
On Thu, 24 Apr 2025 14:51:51 -0400 Konstantin Ryabitsev wrote:
> > Hmm. Looks like pw-bot had too much influence from AI bots
> > and started hallucinating itself :)
>
> I'll look into what happened here.
Alexei mentioned that the bot was stopped, I presume to avoid further
mistakes. I'm 100% sure I've seen the bot be confused by merge commits
before. It happens occasionally, IMHO there is no need to take the bot
offline. Is there an ETA on it coming back?
next prev parent reply other threads:[~2025-04-25 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250424165525.154403-1-iii@linux.ibm.com>
[not found] ` <174551961000.3446286.10420854203925676664.git-patchwork-notify@kernel.org>
2025-04-24 18:41 ` [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock Alexei Starovoitov
2025-04-24 18:51 ` Konstantin Ryabitsev
2025-04-25 16:25 ` Jakub Kicinski [this message]
2025-04-25 17:18 ` Konstantin Ryabitsev
2025-04-25 18:58 ` Konstantin Ryabitsev
2025-04-26 0:32 ` Alexei Starovoitov
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=20250425092551.2891651d@kernel.org \
--to=kuba@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=choypoy@linuxfoundation.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=konstantin@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).