From: Greg Ungerer <gerg@snapgear.com>
To: Fengguang Wu <fengguang.wu@intel.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 23:35:24 +1000 [thread overview]
Message-ID: <502A541C.6090100@snapgear.com> (raw)
In-Reply-To: <20120814051507.GA10244@localhost>
On 08/14/2012 03:15 PM, Fengguang Wu wrote:
> 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!
I'll carry it in the m68knommu git tree, and push to Linus with my
next set of fixes.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
WARNING: multiple messages have this Message-ID (diff)
From: Greg Ungerer <gerg@snapgear.com>
To: Fengguang Wu <fengguang.wu@intel.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 23:35:24 +1000 [thread overview]
Message-ID: <502A541C.6090100@snapgear.com> (raw)
In-Reply-To: <20120814051507.GA10244@localhost>
On 08/14/2012 03:15 PM, Fengguang Wu wrote:
> 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!
I'll carry it in the m68knommu git tree, and push to Linus with my
next set of fixes.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2012-08-14 13:38 UTC|newest]
Thread overview: 6+ 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 4:45 ` gerg
2012-08-14 5:15 ` Fengguang Wu
2012-08-14 13:35 ` Greg Ungerer [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=502A541C.6090100@snapgear.com \
--to=gerg@snapgear.com \
--cc=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--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 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.