From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Move ARCH_HAS_CPU_CACHE_ALIASING
Date: Mon, 6 May 2024 09:49:05 -0400 [thread overview]
Message-ID: <d542207e-4022-4958-9571-375dbcae476a@efficios.com> (raw)
In-Reply-To: <4574ad6cc1117e4b5d29812c165bf7f6e5b60773.1714978406.git.geert@linux-m68k.org>
On 2024-05-06 03:06, Geert Uytterhoeven wrote:
> Move the recently added ARCH_HAS_CPU_CACHE_ALIASING to restore
> alphabetical sort order.
>
> Fixes: 8690bbcf3b7010b3 ("Introduce cpu_dcache_is_aliasing() across all architectures")
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> ---
> To be queued in the m68k tree for v6.10.
>
> arch/m68k/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index c68fbc59787ab59d..e0b4f6e9fe4ce1f4 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -3,8 +3,8 @@ config M68K
> bool
> default y
> select ARCH_32BIT_OFF_T
> - select ARCH_HAS_CPU_CACHE_ALIASING
> select ARCH_HAS_BINFMT_FLAT
> + select ARCH_HAS_CPU_CACHE_ALIASING
> select ARCH_HAS_CPU_FINALIZE_INIT if MMU
> select ARCH_HAS_CURRENT_STACK_POINTER
> select ARCH_HAS_DMA_PREP_COHERENT if M68K_NONCOHERENT_DMA && !COLDFIRE
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2024-05-06 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 7:06 [PATCH] m68k: Move ARCH_HAS_CPU_CACHE_ALIASING Geert Uytterhoeven
2024-05-06 13:49 ` Mathieu Desnoyers [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=d542207e-4022-4958-9571-375dbcae476a@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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).