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 1/5] m68k: Remove duplicate FPU config option
Date: Fri, 8 Jun 2012 11:33:44 +1000 [thread overview]
Message-ID: <4FD15678.3050401@snapgear.com> (raw)
In-Reply-To: <1339094827-12349-1-git-send-email-geert@linux-m68k.org>
On 08/06/12 04:47, Geert Uytterhoeven wrote:
> It's also defined in arch/m68k/Kconfig.cpu
Yep :-)
> Signed-off-by: Geert Uytterhoeven<geert@linux-m68k.org>
Acked-by: Greg Ungerer<gerg@uclinux.org>
Thanks
Greg
> arch/m68k/Kconfig | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index 1471201..bc8cc50 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -62,9 +62,6 @@ config CPU_HAS_NO_MULDIV64
> config CPU_HAS_ADDRESS_SPACES
> bool
>
> -config FPU
> - bool
> -
> config HZ
> int
> default 1000 if CLEOPATRA
--
------------------------------------------------------------------------
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
prev parent reply other threads:[~2012-06-08 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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-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-07 18:47 ` [PATCH 4/5] m68k: Introduce config option CPU_HAS_NO_UNALIGNED Geert Uytterhoeven
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-08 3:51 ` Greg Ungerer
2012-06-08 1:33 ` 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=4FD15678.3050401@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome