linux-kernel - Re: [PATCH 1/2] x86: make voyager_phys_cpu_present

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: <1236790138.3270.41.camel@localhost.localdomain>
Date:	Wed, 11 Mar 2009 16:48:58 +0000
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 1/2] x86: make voyager_phys_cpu_present_map static
	unsigned long.

On Wed, 2009-03-11 at 17:02 +1030, Rusty Russell wrote:
> Impact: cleanup, remove cpumask_t
> 
> Instead of replacing voyager_phys_cpu_present_map with a cpumask_var_t,
> let's make it an unsigned long as assumed in various places anyway.
> 
> Also delete incorrect comment on external usage.

Yes, this looks good.  Having it as a cpumask_t was really a historical
artifact from the time when phys_cpu_present_map was an expected
subarchitecture export.

James


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