public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>
Subject: Re: [Patch] avr32: select GENERIC_ATOMIC64
Date: Fri, 3 Feb 2012 08:36:20 +0100	[thread overview]
Message-ID: <20120203073620.GA13215@samfundet.no> (raw)
In-Reply-To: <1328252580-2630-1-git-send-email-xiyou.wangcong@gmail.com>

Around Fri 03 Feb 2012 15:03:00 +0800 or thereabout, Cong Wang wrote:
> avr32 doesn't implement atomic64_ operations, if not select this,
> we would get:
> 
> kernel/trace/trace_clock.c:117: error: syntax error before 'trace_counter'
> kernel/trace/trace_clock.c:126: error: implicit declaration of function 'atomic64_add_return'
> 
> Cc: Haavard Skinnemoen <hskinnemoen@gmail.com>
> Cc: Hans-Christian Egtvedt <egtvedt@samfundet.no>
> Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>

Thanks Cong, but Fabio beat you to it; https://lkml.org/lkml/2012/2/2/406

The above patch (similar to yours), was just pulled into Andrews tree.

> ---
> diff --git a/arch/avr32/Kconfig b/arch/avr32/Kconfig
> index 197e96f..6ecb8f4 100644
> --- a/arch/avr32/Kconfig
> +++ b/arch/avr32/Kconfig
> @@ -11,6 +11,7 @@ config AVR32
>  	select HARDIRQS_SW_RESEND
>  	select GENERIC_IRQ_SHOW
>  	select ARCH_HAVE_NMI_SAFE_CMPXCHG
> +	select GENERIC_ATOMIC64
>  	help
>  	  AVR32 is a high-performance 32-bit RISC microprocessor core,
>  	  designed for cost-sensitive embedded applications, with particular

-- 
mvh
Hans-Christian Egtvedt

  reply	other threads:[~2012-02-03  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  7:03 [Patch] avr32: select GENERIC_ATOMIC64 Cong Wang
2012-02-03  7:36 ` Hans-Christian Egtvedt [this message]
2012-02-03  7:39   ` Cong Wang

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=20120203073620.GA13215@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=akpm@linux-foundation.org \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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