All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, Greg Ungerer <gerg@uclinux.org>,
	Philippe De Muyter <phdm@macqel.be>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] m68k: Move CPU_HAS_* config options
Date: Fri, 8 Jun 2012 11:38:57 +1000	[thread overview]
Message-ID: <4FD157B1.8050509@snapgear.com> (raw)
In-Reply-To: <1339094827-12349-2-git-send-email-geert@linux-m68k.org>

On 08/06/12 04:47, Geert Uytterhoeven wrote:
> They belong together with the CPU selection
>
> Signed-off-by: Geert Uytterhoeven<geert@linux-m68k.org>

Acked-by: Greg Ungerer<gerg@uclinux.org>

Regards
Greg


>   arch/m68k/Kconfig     |    9 ---------
>   arch/m68k/Kconfig.cpu |    9 +++++++++
>   2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index bc8cc50..87b504c 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -53,15 +53,6 @@ config ZONE_DMA
>   	bool
>   	default y
>
> -config CPU_HAS_NO_BITFIELDS
> -	bool
> -
> -config CPU_HAS_NO_MULDIV64
> -	bool
> -
> -config CPU_HAS_ADDRESS_SPACES
> -	bool
> -
>   config HZ
>   	int
>   	default 1000 if CLEOPATRA
> diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
> index 2b53254..6cd8c1a 100644
> --- a/arch/m68k/Kconfig.cpu
> +++ b/arch/m68k/Kconfig.cpu
> @@ -360,6 +360,15 @@ config NODES_SHIFT
>   	default "3"
>   	depends on !SINGLE_MEMORY_CHUNK
>
> +config CPU_HAS_NO_BITFIELDS
> +	bool
> +
> +config CPU_HAS_NO_MULDIV64
> +	bool
> +
> +config CPU_HAS_ADDRESS_SPACES
> +	bool
> +
>   config FPU
>   	bool
>


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

WARNING: multiple messages have this Message-ID (diff)
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <linux-m68k@vger.kernel.org>, Greg Ungerer <gerg@uclinux.org>,
	Philippe De Muyter <phdm@macqel.be>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] m68k: Move CPU_HAS_* config options
Date: Fri, 8 Jun 2012 11:38:57 +1000	[thread overview]
Message-ID: <4FD157B1.8050509@snapgear.com> (raw)
In-Reply-To: <1339094827-12349-2-git-send-email-geert@linux-m68k.org>

On 08/06/12 04:47, Geert Uytterhoeven wrote:
> They belong together with the CPU selection
>
> Signed-off-by: Geert Uytterhoeven<geert@linux-m68k.org>

Acked-by: Greg Ungerer<gerg@uclinux.org>

Regards
Greg


>   arch/m68k/Kconfig     |    9 ---------
>   arch/m68k/Kconfig.cpu |    9 +++++++++
>   2 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index bc8cc50..87b504c 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -53,15 +53,6 @@ config ZONE_DMA
>   	bool
>   	default y
>
> -config CPU_HAS_NO_BITFIELDS
> -	bool
> -
> -config CPU_HAS_NO_MULDIV64
> -	bool
> -
> -config CPU_HAS_ADDRESS_SPACES
> -	bool
> -
>   config HZ
>   	int
>   	default 1000 if CLEOPATRA
> diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
> index 2b53254..6cd8c1a 100644
> --- a/arch/m68k/Kconfig.cpu
> +++ b/arch/m68k/Kconfig.cpu
> @@ -360,6 +360,15 @@ config NODES_SHIFT
>   	default "3"
>   	depends on !SINGLE_MEMORY_CHUNK
>
> +config CPU_HAS_NO_BITFIELDS
> +	bool
> +
> +config CPU_HAS_NO_MULDIV64
> +	bool
> +
> +config CPU_HAS_ADDRESS_SPACES
> +	bool
> +
>   config FPU
>   	bool
>


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  reply	other threads:[~2012-06-08  1:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 18:47 [PATCH 1/5] m68k: Remove duplicate FPU config option Geert Uytterhoeven
2012-06-07 18:47 ` Geert Uytterhoeven
2012-06-07 18:47 ` [PATCH 2/5] m68k: Move CPU_HAS_* config options Geert Uytterhoeven
2012-06-07 18:47   ` Geert Uytterhoeven
2012-06-08  1:38   ` Greg Ungerer [this message]
2012-06-08  1:38     ` Greg Ungerer
2012-06-07 18:47 ` [PATCH 3/5] m68k: delay, muldi3 - Use CONFIG_CPU_HAS_NO_MULDIV64 Geert Uytterhoeven
2012-06-08  3:48   ` Greg Ungerer
2012-06-08  3:48     ` Greg Ungerer
2012-06-07 18:47 ` Geert Uytterhoeven
2012-06-07 18:47 ` [PATCH 4/5] m68k: Introduce config option CPU_HAS_NO_UNALIGNED Geert Uytterhoeven
2012-06-07 18:47   ` Geert Uytterhoeven
2012-06-08  3:50   ` Greg Ungerer
2012-06-08  3:50     ` Greg Ungerer
2012-06-07 18:47 ` [PATCH 5/5] m68k: CPU32 does not support unaligned accesses Geert Uytterhoeven
2012-06-07 18:47   ` Geert Uytterhoeven
2012-06-08  3:51   ` Greg Ungerer
2012-06-08  3:51     ` Greg Ungerer
2012-06-08  1:33 ` [PATCH 1/5] m68k: Remove duplicate FPU config option Greg Ungerer
2012-06-08  1:33   ` Greg Ungerer

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=4FD157B1.8050509@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=phdm@macqel.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.