From: bot+bpf-ci@kernel.org
To: jolsa@kernel.org,andrii@kernel.org
Cc: bpf@vger.kernel.org,linux-kernel@vger.kernel.org,songliubraving@fb.com,yhs@fb.com,john.fastabend@gmail.com,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,clm@meta.com,ihor.solodrai@linux.dev
Subject: Re: [PATCHv2 bpf-next 3/5] selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch
Date: Tue, 10 Feb 2026 14:12:07 +0000 (UTC) [thread overview]
Message-ID: <028617ef5663bf2f9901701630d223fed88e519d2020e3317bfffb4ef5cb123b@mail.kernel.org> (raw)
In-Reply-To: <20260210133649.524292-4-jolsa@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
> selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch
This isn't a bug, but there's a typo in the subject line. "no5" should
be "nop5".
> Now that we have no5 optimization support in kernel, let's emit
The same typo appears here in the commit body.
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/21867569087
AI-authorship-score: low
AI-authorship-explanation: The commit shows typical human development patterns including a typo in the commit message, iterative design changes between v1 and v2 based on real-world testing, and normal kernel mailing list review interactions.
issues-found: 1
issue-severity-score: low
issue-severity-explanation: Single typo in commit message subject and body where 'no5' should be 'nop5'; does not affect code functionality.
next prev parent reply other threads:[~2026-02-10 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:36 [PATCHv2 bpf-next 0/5] libbpf: Make optimized uprobes backward compatible Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 1/5] libbpf: Add uprobe syscall feature detection Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 2/5] libbpf: Add support to detect nop,nop5 instructions combo for usdt probe Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 3/5] selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci [this message]
2026-02-10 13:36 ` [PATCHv2 bpf-next 4/5] selftests/bpf: Add test for checking correct nop of optimized usdt Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci
2026-02-10 21:22 ` Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 5/5] selftests/bpf: Add usdt trigger bench Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci
2026-02-10 21:41 ` Jiri Olsa
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=028617ef5663bf2f9901701630d223fed88e519d2020e3317bfffb4ef5cb123b@mail.kernel.org \
--to=bot+bpf-ci@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--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
all inboxes | Powered by JetHome®