From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the loongarch tree
Date: Mon, 31 Jul 2023 07:51:55 +1000 [thread overview]
Message-ID: <20230731075155.739e5a2c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
bdc86a68be08 ("LoongArch: Cleanup __builtin_constant_p() checking for cpu_has_*")
a9b000c11611 ("LoongArch: BPF: Fix check condition to call lu32id in move_imm()")
27a4ebe0b5ed ("LoongArch: BPF: Enable bpf_probe_read{, str}() on LoongArch")
1bdb8a673df0 ("LoongArch: Fix return value underflow in exception path")
afd22cada106 ("LoongArch: Fix CMDLINE_EXTEND and CMDLINE_BOOTLOADER handling")
d4a1397e5d61 ("LoongArch: Fix module relocation error with binutils 2.41")
4d57f619c06b ("LoongArch: Only fiddle with CHECKFLAGS if `need-compiler'")
These are commits
1e74ae32805b ("LoongArch: Cleanup __builtin_constant_p() checking for cpu_has_*")
4eece7e6de94 ("LoongArch: BPF: Fix check condition to call lu32id in move_imm()")
de0e30bee86d ("LoongArch: BPF: Enable bpf_probe_read{, str}() on LoongArch")
e66d511fc922 ("LoongArch: Fix return value underflow in exception path")
83da30d73b86 ("LoongArch: Fix CMDLINE_EXTEND and CMDLINE_BOOTLOADER handling")
03c53eb90c0c ("LoongArch: Fix module relocation error with binutils 2.41")
54c2c9df083f ("LoongArch: Only fiddle with CHECKFLAGS if `need-compiler'")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-07-30 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 21:51 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 2:02 linux-next: duplicate patches in the loongarch tree Stephen Rothwell
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=20230731075155.739e5a2c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).