From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chen Gang Subject: Re: [Suggestion] arch/*/include/asm/bitops.h: about __set_bit() API. Date: Thu, 13 Jun 2013 10:30:33 +0800 Message-ID: <51B92EC9.3050003@asianux.com> References: <51B30285.6020503@asianux.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51B30285.6020503@asianux.com> Sender: linux-arch-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: rth@twiddle.net, ink@jurassic.park.msu.ru, mattst88@gmail.com, "dhowells@redhat.com" , tony.luck@intel.com, fenghua.yu@intel.com, yasutake.koichi@jp.panasonic.com Cc: linux-alpha@vger.kernel.org, "linux-kernel@vger.kernel.org" , linux-ia64@vger.kernel.org, linux-am33-list@redhat.com, Linux-Arch On 06/08/2013 06:08 PM, Chen Gang wrote: > Several architectures have different __set_bit() API to others, in > standard API, 2nd param of __set_bit() is 'unsigned long *', but: > > in 'min10300', it is 'unsigned char *', Oh, it is my fault, for 'mn10300' it is no issue, it is not 'unsigned char *' (it is a generic one which can match any type). Also 'min10300' --> 'mn10300'. Thanks. -- Chen Gang Asianux Corporation