From: Fengguang Wu <fengguang.wu@intel.com>
To: gerg@snapgear.com
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
geert@linux-m68k.org, ebiederm@xmission.com,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: select CONFIG_GENERIC_ATOMIC64 for all m68k CPU types
Date: Tue, 14 Aug 2012 13:15:07 +0800 [thread overview]
Message-ID: <20120814051507.GA10244@localhost> (raw)
In-Reply-To: <1344919533-9357-1-git-send-email-gerg@snapgear.com>
On Tue, Aug 14, 2012 at 02:45:33PM +1000, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> There is no specific atomic64 support code for any m68k CPUs, so we should
> select CONFIG_GENERIC_ATOMC64 for all. Remove the existing per CPU selection
> of this and select it for all m68k.
>
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Thanks for the complete solution!
next prev parent reply other threads:[~2012-08-14 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 4:45 [PATCH] m68k: select CONFIG_GENERIC_ATOMIC64 for all m68k CPU types gerg
2012-08-14 5:15 ` Fengguang Wu [this message]
2012-08-14 13:35 ` Greg Ungerer
2012-08-14 7:52 ` Geert Uytterhoeven
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=20120814051507.GA10244@localhost \
--to=fengguang.wu@intel.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.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