linux-kernel - Re: [PATCH] cpumask: remove __first_cpu / __next

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] [day] [month] [year] [list]

Message-Id: <20150416.152614.2206192390901163987.davem@davemloft.net>
Date:	Thu, 16 Apr 2015 15:26:14 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	rusty@...tcorp.com.au
Cc:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpumask: remove __first_cpu / __next_cpu

From: Rusty Russell <rusty@...tcorp.com.au>
Date: Thu, 16 Apr 2015 14:13:32 +0930

> [ Final grep before push to Linus revealed sparc used these directly,
>   please Ack.  Against my cpumask-next tree. ]
> 
> They were for use by the deprecated first_cpu() and next_cpu() wrappers,
> but sparc used them directly.
> 
> They're now replaced by cpumask_first / cpumask_next.  And __next_cpu_nr
> is completely obsolete.
> 
> Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>

Acked-by: David S. Miller <davem@...emloft.net>

--
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/