linux-kernel - Re: [PATCH 13/16] percpu: remove per_cpu_

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]

Message-ID: <4AE9855C.50709@kernel.org>
Date:	Thu, 29 Oct 2009 13:06:52 +0100
From:	Tejun Heo <tj@...nel.org>
To:	monstr@...str.eu
CC:	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au,
	mingo@...hat.com, Thomas Gleixner <tglx@...utronix.de>,
	akpm@...ux-foundation.org, rostedt@...dmis.org, hpa@...or.com,
	cebbert@...hat.com, tony.luck@...el.com
Subject: Re: [PATCH 13/16] percpu: remove per_cpu__ prefix.

Michal Simek wrote:
> If I understand correctly, functionality will be the same. But
> anyway I would like to mot lose information about per_cpu
> variables. That's why please keep that macro for Microblaze. If is
> the problem, you should convince me why to do it.

It's not a problem at all.  The only thing is that now there's nothing
which enforces usage of that macro in assemblies.  If someone forgets
to use that macro, it will work all the same.  It would be great if we
can fix it somehow but I don't have much idea ATM.  Anyways, for now,
I'll proceed in the current form.

Thanks.

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