[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51B92EC9.3050003@asianux.com>
Date: Thu, 13 Jun 2013 10:30:33 +0800
From: Chen Gang <gang.chen@...anux.com>
To: rth@...ddle.net, ink@...assic.park.msu.ru, mattst88@...il.com,
"dhowells@...hat.com" <dhowells@...hat.com>, tony.luck@...el.com,
fenghua.yu@...el.com, yasutake.koichi@...panasonic.com
CC: linux-alpha@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-ia64@...r.kernel.org, linux-am33-list@...hat.com,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [Suggestion] arch/*/include/asm/bitops.h: about __set_bit() API.
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists