Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752408Ab2HNNih (ORCPT ); Tue, 14 Aug 2012 09:38:37 -0400 Received: from dalsmrelay2.nai.com ([205.227.136.216]:59057 "EHLO dalsmrelay2.nai.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751963Ab2HNNif (ORCPT ); Tue, 14 Aug 2012 09:38:35 -0400 Message-ID: <502A541C.6090100@snapgear.com> Date: Tue, 14 Aug 2012 23:35:24 +1000 From: Greg Ungerer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Fengguang Wu CC: , , , , Greg Ungerer Subject: Re: [PATCH] m68k: select CONFIG_GENERIC_ATOMIC64 for all m68k CPU types References: <1344919533-9357-1-git-send-email-gerg@snapgear.com> <20120814051507.GA10244@localhost> In-Reply-To: <20120814051507.GA10244@localhost> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1215 Lines: 31 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 >> >> 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 > > Signed-off-by: Fengguang Wu > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/