From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: stable <stable@vger.kernel.org>,
chenhuacai <chenhuacai@kernel.org>,
loongarch <loongarch@lists.linux.dev>
Subject: Re: [PATCH 6.6] Revert "LoongArch: BPF: Sign extend kfunc call arguments"
Date: Thu, 15 Jan 2026 12:38:45 +0100 [thread overview]
Message-ID: <2026011537-that-theater-3b05@gregkh> (raw)
In-Reply-To: <tencent_2AA9934C60F1658F28275258@qq.com>
On Wed, Jan 14, 2026 at 02:24:15PM +0800, Wentao Guan wrote:
> Hello All,
>
> I think the best way is backport add28024405ed600afaa02749989d4fd119f9057,
> ("LoongArch: Add more instruction opcodes and emit_* helpers")
> I test when cherry-pick it, it build ok.
Great, I'll do that instead, thanks!
greg k-h
next prev parent reply other threads:[~2026-01-15 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 6:13 [PATCH 6.6] Revert "LoongArch: BPF: Sign extend kfunc call arguments" Wentao Guan
2026-01-14 6:24 ` Wentao Guan
2026-01-15 11:38 ` Greg KH [this message]
2026-01-30 10:04 ` [PATCH 6.6] ALSA: usb-audio: Fix missing unlock at error path of maxpacksize check Wentao Guan
2026-02-03 14:48 ` Greg KH
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=2026011537-that-theater-3b05@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenhuacai@kernel.org \
--cc=guanwentao@uniontech.com \
--cc=loongarch@lists.linux.dev \
--cc=stable@vger.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