linux-kernel - Re: [PATCH] drivers: acpi: make ACPI_PROCFS

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 15 May 2015 02:02 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Hanjun Guo <hanjun.guo@...aro.org>
Cc:	Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Lan Tianyu <tianyu.lan@...el.com>
Subject: Re: [PATCH] drivers: acpi: make ACPI_PROCFS_POWER X86 only

On Saturday, May 02, 2015 09:09:35 PM Hanjun Guo wrote:
> On 2015年05月01日 18:27, Lorenzo Pieralisi wrote:
> > The ACPI procfs power interface is initialized by compilation units
> > that are only selectable on X86 platforms. Since its usage is
> > deprecated and it cannot even be used on platforms other than X86
> > it should be compiled in only on X86 platforms.
> >
> > This patch makes CONFIG_ACPI_PROCFS_POWER dependent on X86, so
> > that other architectures are prevented from compiling it in for
> > no purpose.
> >
> > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
> > Cc: Hanjun Guo <hanjun.guo@...aro.org>
> > Cc: Lan Tianyu <tianyu.lan@...el.com>
> > Cc: Rafael J. Wysocki <rjw@...ysocki.net>
> 
> I think this proc fs was not used for IA64 (it is
> for server platform) too.
> 
> Acked-by: Hanjun Guo <hanjun.guo@...aro.org>

Queued up for 4.2, thanks!


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/