From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 1/2][MIPS] Update asm string header
Date: Tue, 28 Aug 2007 19:11:53 +0900 [thread overview]
Message-ID: <46D3F4E9.5000403@necel.com> (raw)
In-Reply-To: <20070827124120.D554424047@gemini.denx.de>
Wolfgang Denk wrote:
> In message <46D295EF.3030003@necel.com> you wrote:
>> [MIPS] Update asm string header
>>
>> From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
>>
>> This includes several bugfixes and cleanups in the latest upstream:
> ...
>> diff --git a/include/asm-mips/string.h b/include/asm-mips/string.h
>> index 463a111..4739c18 100644
>> --- a/include/asm-mips/string.h
>> +++ b/include/asm-mips/string.h
>> @@ -1,18 +1,26 @@
> ...
>> +/*
>> + * Most of the inline functions are rather naive implementations so I just
>> + * didn't bother updating them for 64-bit ...
>> */
>> -#ifndef __ASM_MIPS_STRING_H
>> -#define __ASM_MIPS_STRING_H
>> +#if 1 /* #ifdef CONFIG_32BIT */
>
> Please remove this (and the corresponding #endif).
I just wanted to indicate that this funcs is valid for 32-bit mode.
But, I agree that it's not a proper workaround.
> Ummm... does this work on 64 bit MIPS systems, too?
No it doesn't, according to the upstream's decision.
Unfortunately, AFAIK, current MIPS port doesn't have general configs
for 32/64-bit mode. It might be better to use lib_generic/string.c for
both CPU mode in this situation.
Thanks,
Shinya Kuribayashi
next prev parent reply other threads:[~2007-08-28 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 9:14 [U-Boot-Users] [PATCH 1/2][MIPS] Update asm string header Shinya Kuribayashi
2007-08-27 12:41 ` Wolfgang Denk
2007-08-28 10:11 ` Shinya Kuribayashi [this message]
2007-08-28 14:31 ` Wolfgang Denk
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=46D3F4E9.5000403@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=u-boot@lists.denx.de \
/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.