From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, chenhuacai@loongson.cn
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH for 6.1/6.6] LoongArch: Explicitly specify code model in Makefile
Date: Tue, 13 May 2025 14:49:55 -0400 [thread overview]
Message-ID: <20250513113647-90f20a5797414ec0@stable.kernel.org> (raw)
In-Reply-To: <20250513080645.252607-1-chenhuacai@loongson.cn>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: e67e0eb6a98b261caf45048f9eb95fd7609289c0
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 7b3a7918f10d)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: e67e0eb6a98b2 ! 1: fa2ca06c43c1a LoongArch: Explicitly specify code model in Makefile
@@ arch/loongarch/Makefile: endif
+cflags-y += -mabi=lp64s -mcmodel=normal
endif
- cflags-y += -pipe $(CC_FLAGS_NO_FPU)
-@@ arch/loongarch/Makefile: ifdef CONFIG_OBJTOOL
- KBUILD_CFLAGS += -fno-jump-tables
- endif
-
--KBUILD_RUSTFLAGS += --target=loongarch64-unknown-none-softfloat
-+KBUILD_RUSTFLAGS += --target=loongarch64-unknown-none-softfloat -Ccode-model=small
- KBUILD_RUSTFLAGS_KERNEL += -Zdirect-access-external-data=yes
- KBUILD_RUSTFLAGS_MODULE += -Zdirect-access-external-data=no
-
+ cflags-y += -pipe -msoft-float
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-05-13 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:06 [PATCH for 6.1/6.6] LoongArch: Explicitly specify code model in Makefile Huacai Chen
2025-05-13 8:12 ` Greg Kroah-Hartman
2025-05-13 18:49 ` Sasha Levin [this message]
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=20250513113647-90f20a5797414ec0@stable.kernel.org \
--to=sashal@kernel.org \
--cc=chenhuacai@loongson.cn \
--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