linux-kernel - Re: [PATCH] cpumask: add a few comments of cpumask functions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 May 2012 06:49:57 -0400
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Alex Shi <alex.shi@...el.com>
Cc:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	rusty@...tcorp.com.au, akpm@...ux-foundation.org,
	paul.gortmaker@...driver.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpumask: add a few comments of cpumask functions

On Wed, May 30, 2012 at 6:40 AM, Alex Shi <alex.shi@...el.com> wrote:
> On 05/29/2012 09:16 AM, Alex Shi wrote:
>
>>
>>>>> s/return/Returns
>>>>>
>>>>> What do you mean by "old" cpumask?
>>>>
>>>> Thanks for comments!
>>>> Should be "the old bitmap of cpumask"?
>>>>
>>>
>>>
>>> No, there is no "old" or "new" cpumask here because this function doesn't
>>> change the cpumask. It just checks if that bit is set.
>>> So something like:
>>> Returns 1 if 'cpu' is set in 'cpumask', else returns 0.
>>>
>>
>>
>>
>> Sure, thanks! and comments changed again following your style.
>> Is the following new update patch ok?
>
>
> Any further comments for this patch? :)

Acked-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
--
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/