public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Chen Gang <gang.chen@asianux.com>
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: Fri, 19 Apr 2013 14:12:54 +0200	[thread overview]
Message-ID: <201304191412.54601.arnd@arndb.de> (raw)
In-Reply-To: <51712E5E.2020809@asianux.com>

On Friday 19 April 2013, Chen Gang wrote:
> in arch/arm64/include/asm, not define the function cmpxchg64
> 
>   when compiling with allmodconfig,
>     drivers/block/blockconsole.c will need this function.
> 
>   I am not quite familiar with ARM64 (neither ARM64 assembler)
> 
>   can any member helps to send related patch ?
>     if no one have time to send related patch, I should try.
>     and I am glad to try, but need additional time resources,
>     if I try, I should finish it within this month (2013-4-30).
> 
>   welcome any suggestions or completions.

cmpxchg64 is the same as cmpxchg on 64-bit platforms, can't the
driver be changed to use the latter?

	Arnd

  reply	other threads:[~2013-04-19 12:13 UTC|newest]

Thread overview: 8+ 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 12:12 ` Arnd Bergmann [this message]
2013-04-20  2:28   ` Chen Gang
2013-04-20  7:32     ` Arnd Bergmann
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-23 10:48         ` Catalin Marinas
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=201304191412.54601.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Catalin.Marinas@arm.com \
    --cc=gang.chen@asianux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.com \
    --cc=will.deacon@arm.com \
    /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