From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language.
Date: Mon, 22 Apr 2013 13:08:22 +0800 [thread overview]
Message-ID: <5174C5C6.5010206@asianux.com> (raw)
In-Reply-To: <2182812.ymprEm6XBb@wuerfel>
On 2013?04?20? 15:32, Arnd Bergmann wrote:
> On Saturday 20 April 2013 10:28:55 Chen Gang wrote:
>>
>> -------------------------------patch begin--------------------------------------
>>
>> diff --git a/arch/arm64/include/asm/cmpxchg.h b/arch/arm64/include/asm/cmpxchg.h
>> index 968b5cb..b572d2b 100644
>> --- a/arch/arm64/include/asm/cmpxchg.h
>> +++ b/arch/arm64/include/asm/cmpxchg.h
>> @@ -170,4 +170,6 @@ static inline unsigned long __cmpxchg_mb(volatile void *ptr, unsigned long old,
>> (unsigned long)(n), \
>> sizeof(*(ptr))))
>>
>> +#define cmpxchg64(ptr,o,n) cmpxchg((ptr),(o),(n))
>> +
>> #endif /* __ASM_CMPXCHG_H */
>
> Yes, this looks good. Please provide the same for cmpxchg64_local.
>
ok, thanks, I will send related patch.
gchen.
WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Tony Lindgren <tony@atomide.com>,
"olof@lixom.net" <olof@lixom.net>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language.
Date: Mon, 22 Apr 2013 13:08:22 +0800 [thread overview]
Message-ID: <5174C5C6.5010206@asianux.com> (raw)
In-Reply-To: <2182812.ymprEm6XBb@wuerfel>
On 2013年04月20日 15:32, Arnd Bergmann wrote:
> On Saturday 20 April 2013 10:28:55 Chen Gang wrote:
>>
>> -------------------------------patch begin--------------------------------------
>>
>> diff --git a/arch/arm64/include/asm/cmpxchg.h b/arch/arm64/include/asm/cmpxchg.h
>> index 968b5cb..b572d2b 100644
>> --- a/arch/arm64/include/asm/cmpxchg.h
>> +++ b/arch/arm64/include/asm/cmpxchg.h
>> @@ -170,4 +170,6 @@ static inline unsigned long __cmpxchg_mb(volatile void *ptr, unsigned long old,
>> (unsigned long)(n), \
>> sizeof(*(ptr))))
>>
>> +#define cmpxchg64(ptr,o,n) cmpxchg((ptr),(o),(n))
>> +
>> #endif /* __ASM_CMPXCHG_H */
>
> Yes, this looks good. Please provide the same for cmpxchg64_local.
>
ok, thanks, I will send related patch.
gchen.
next prev parent reply other threads:[~2013-04-22 5:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 11:45 [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language Chen Gang
2013-04-19 11:45 ` Chen Gang
2013-04-19 12:12 ` Arnd Bergmann
2013-04-19 12:12 ` Arnd Bergmann
2013-04-20 2:28 ` Chen Gang
2013-04-20 2:28 ` Chen Gang
2013-04-20 7:32 ` Arnd Bergmann
2013-04-20 7:32 ` Arnd Bergmann
2013-04-22 5:08 ` Chen Gang [this message]
2013-04-22 5:08 ` Chen Gang
2013-04-22 5:08 ` [PATCH] ARM64: kernel: compiling issue, define cmpxchg64 and cmpxchg64_local for outside using Chen Gang
2013-04-22 5:08 ` Chen Gang
2013-04-23 10:48 ` Catalin Marinas
2013-04-23 10:48 ` Catalin Marinas
2013-04-23 10:54 ` Chen Gang
2013-04-23 10:54 ` Chen Gang
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=5174C5C6.5010206@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.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 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.