public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68knommu: Remove MCPU32 config symbol
Date: Mon, 4 Oct 2021 21:29:01 +1000	[thread overview]
Message-ID: <41cd6008-75c8-1fa7-dfc3-3bf843707db3@linux-m68k.org> (raw)
In-Reply-To: <20211004070231.2943362-1-geert@linux-m68k.org>

On 4/10/21 5:02 pm, Geert Uytterhoeven wrote:
> As of commit a3595962d82495f5 ("m68knommu: remove obsolete 68360
> support"), nothing selects MCPU32 anymore.
> 
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>

Thanks Geert. I'll push it into the m68knommu git tree.

Regards
Greg


>   arch/m68k/Kconfig.cpu          | 11 -----------
>   arch/m68k/include/asm/bitops.h |  2 +-
>   2 files changed, 1 insertion(+), 12 deletions(-)
> 
> diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
> index 277d61a094637ce3..0d00ef5117dceed9 100644
> --- a/arch/m68k/Kconfig.cpu
> +++ b/arch/m68k/Kconfig.cpu
> @@ -53,17 +53,6 @@ config M68000
>   	  System-On-Chip devices (eg 68328, 68302, etc). It does not contain
>   	  a paging MMU.
>   
> -config MCPU32
> -	bool
> -	select CPU_HAS_NO_BITFIELDS
> -	select CPU_HAS_NO_CAS
> -	select CPU_HAS_NO_UNALIGNED
> -	select CPU_NO_EFFICIENT_FFS
> -	help
> -	  The Freescale (was then Motorola) CPU32 is a CPU core that is
> -	  based on the 68020 processor. For the most part it is used in
> -	  System-On-Chip parts, and does not contain a paging MMU.
> -
>   config M68020
>   	bool "68020 support"
>   	depends on MMU
> diff --git a/arch/m68k/include/asm/bitops.h b/arch/m68k/include/asm/bitops.h
> index 7b414099e5fc20fa..7b93e1fd8ffa902f 100644
> --- a/arch/m68k/include/asm/bitops.h
> +++ b/arch/m68k/include/asm/bitops.h
> @@ -451,7 +451,7 @@ static inline unsigned long ffz(unsigned long word)
>    *	generic functions for those.
>    */
>   #if (defined(__mcfisaaplus__) || defined(__mcfisac__)) && \
> -	!defined(CONFIG_M68000) && !defined(CONFIG_MCPU32)
> +	!defined(CONFIG_M68000)
>   static inline unsigned long __ffs(unsigned long x)
>   {
>   	__asm__ __volatile__ ("bitrev %0; ff1 %0"
> 


      reply	other threads:[~2021-10-04 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04  7:02 [PATCH] m68knommu: Remove MCPU32 config symbol Geert Uytterhoeven
2021-10-04 11:29 ` Greg Ungerer [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=41cd6008-75c8-1fa7-dfc3-3bf843707db3@linux-m68k.org \
    --to=gerg@linux-m68k.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