linux-kernel - Re: [PATCH -tip 0/7] x86 rename mpc_config_X to mpc

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: <20090104110725.GA24454@elte.hu>
Date:	Sun, 4 Jan 2009 12:07:25 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...radead.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andi Kleen <andi@...stfloor.org>, astarikovskiy@...e.de,
	jbarnes@....com, pazke@...ita1.ru,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip 0/7] x86 rename mpc_config_X to mpc_X


* Jaswinder Singh Rajput <jaswinder@...radead.org> wrote:

> These are first set of patches for cleanup related to mpspec as suggested by Ingo Molnar.
> Once these are approved and applied then I will send next set of patches.
> 
> The following changes since commit 6ea161d36b1a3615f10a52bd5b19fac41653eea4:
>   Ingo Molnar (1):
>         Merge branch 'linus'
> 
> Jaswinder Singh Rajput (7):
>       x86: rename mp_config_table to mpc_table
>       x86: rename mpc_config_bus to mpc_bus
>       x86: rename mpc_config_processor to mpc_cpu
>       x86: rename mpc_config_ioapic to mpc_ioapic
>       x86: rename mpc_config_intsrc to mpc_intsrc
>       x86: rename mpc_config_lintsrc to mpc_lintsrc
>       x86: rename mpc_config_oemtable to mpc_oemtable

i'm wondering, will you also try the other, more structural cleanups i 
suggested?

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