From: patchwork-bot+netdevbpf@kernel.org
To: Johan Almbladh <johan.almbladh@anyfinetworks.com>
Cc: tsbogend@alpha.franken.de, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
paulburton@kernel.org, main.kalliope@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, philmd@oss.qualcomm.com
Subject: Re: [PATCH bpf 1/2] bpf, mips: Fix immediate JMP JEQ/JNE on MIPS32
Date: Thu, 24 Sep 2026 02:00:05 +0000 [thread overview]
Message-ID: <179021520541.1274904.9859067781953002975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260923105158.3514342-1-johan.almbladh@anyfinetworks.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 23 Sep 2026 12:51:57 +0200 you wrote:
> An addu instruction was emitted instead of addiu, causing the immediate
> value 1 to be interpreted as register $at. This made the comparison
> result invalid when the immediate operand was negative. Note that $at
> is mapped to BPF_REG_AX, which is used for constant blinding.
>
> Fix the instruction to use the immediate form.
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf, mips: Fix immediate JMP JEQ/JNE on MIPS32
https://git.kernel.org/bpf/bpf/c/db762fd96be2
- [bpf,2/2] bpf, mips: Fix BSWAP 32 and 16 on MIPS64
https://git.kernel.org/bpf/bpf/c/8110ba097778
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-24 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:51 Johan Almbladh
2026-09-23 10:51 ` [PATCH bpf 2/2] bpf, mips: Fix BSWAP 32 and 16 on MIPS64 Johan Almbladh
2026-09-24 2:00 ` patchwork-bot+netdevbpf [this message]
2026-09-24 8:22 ` [PATCH bpf 1/2] bpf, mips: Fix immediate JMP JEQ/JNE on MIPS32 David Laight
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=179021520541.1274904.9859067781953002975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@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=johan.almbladh@anyfinetworks.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=main.kalliope@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=paulburton@kernel.org \
--cc=philmd@oss.qualcomm.com \
--cc=song@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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®