From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Keguang Zhang <keguang.zhang@gmail.com>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: LOONGSON32: drop a dangling Kconfig symbol
Date: Fri, 30 Jan 2026 15:34:29 +0100 [thread overview]
Message-ID: <aXzBdfjPC0patZd9@alpha.franken.de> (raw)
In-Reply-To: <20251228190443.2479978-1-rdunlap@infradead.org>
On Sun, Dec 28, 2025 at 11:04:43AM -0800, Randy Dunlap wrote:
> CPU_GAS_LOAD_STORE_LR is not used anywhere in the kernel sources,
> so drop it.
>
> Fixes: 85c4354076ca ("MIPS: loongson32: Switch to generic core")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Keguang Zhang <keguang.zhang@gmail.com>
> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> Cc: linux-mips@vger.kernel.org
>
> arch/mips/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> --- linux-next-20251219.orig/arch/mips/Kconfig
> +++ linux-next-20251219/arch/mips/Kconfig
> @@ -1408,7 +1408,6 @@ config CPU_LOONGSON32
> select CPU_MIPS32
> select CPU_MIPSR2
> select CPU_HAS_PREFETCH
> - select CPU_HAS_LOAD_STORE_LR
> select CPU_SUPPORTS_32BIT_KERNEL
> select CPU_SUPPORTS_HIGHMEM
> select CPU_SUPPORTS_CPUFREQ
applied to mips-next with the typo fixed
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-01-30 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 19:04 [PATCH] mips: LOONGSON32: drop a dangling Kconfig symbol Randy Dunlap
2025-12-30 2:33 ` Keguang Zhang
2026-01-03 1:26 ` Maciej W. Rozycki
2026-01-03 4:23 ` Randy Dunlap
2026-01-30 14:34 ` Thomas Bogendoerfer [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=aXzBdfjPC0patZd9@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=keguang.zhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rdunlap@infradead.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