From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Define __arch_swab64 for all mips r2 cpus.
Date: Sun, 28 Jun 2009 19:50:48 +0100 [thread overview]
Message-ID: <20090628185048.GB23369@linux-mips.org> (raw)
In-Reply-To: <1246032168-31411-1-git-send-email-ddaney@caviumnetworks.com>
On Fri, Jun 26, 2009 at 09:02:48AM -0700, David Daney wrote:
> Some CPUs implement mipsr2, but because they are a super-set of
> mips64r2 do not define CONFIG_CPU_MIPS64_R2. Cavium OCTEON falls into
> this category. We would still like to use the optimized
> implementation, so since we have already checked for
> CONFIG_CPU_MIPSR2, checking for CONFIG_64BIT instead of
> CONFIG_CPU_MIPS64_R2 is sufficient.
>
> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
> ---
> arch/mips/include/asm/swab.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/mips/include/asm/swab.h b/arch/mips/include/asm/swab.h
> index 99993c0..e5b9161 100644
> --- a/arch/mips/include/asm/swab.h
> +++ b/arch/mips/include/asm/swab.h
> @@ -38,7 +38,7 @@ static inline __attribute_const__ __u32 __arch_swab32(__u32 x)
> }
> #define __arch_swab32 __arch_swab32
>
> -#ifdef CONFIG_CPU_MIPS64_R2
> +#ifdef CONFIG_64BIT
You just broke support for non-R2 64-bit processors.
Ralf
next prev parent reply other threads:[~2009-06-28 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 16:02 [PATCH] MIPS: Define __arch_swab64 for all mips r2 cpus David Daney
2009-06-28 18:50 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-17 20:44 David Daney
2008-12-17 21:20 ` David Daney
2008-12-18 8:07 ` Ralf Baechle
2008-12-18 16:42 ` David Daney
2008-12-18 17:06 ` Ralf Baechle
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=20090628185048.GB23369@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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 NNTP newsgroup(s).