linux-kernel - Re: [PATCH] ACPI: remove unused ACPI

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

Message-ID: <1382948855.32195.9.camel@x220.thuisdomein>
Date:	Mon, 28 Oct 2013 09:27:35 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Michael Opdenacker <michael.opdenacker@...e-electrons.com>
Cc:	Lan Tianyu <lantianyu1986@...il.com>, Len Brown <lenb@...nel.org>,
	rjw@...ysocki.net,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r kernel org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ACPI: remove unused ACPI_PROCFS Kconfig param

On Mon, 2013-10-28 at 07:22 +0100, Michael Opdenacker wrote:
> [...] CONFIG_ACPI_PROCFS is no longer used anywhere, neither in
> Makefiles nor in the source code. ACPI_PROCFS isn't event used in
> Kconfig files as an intermediate dependency.
> 
> What I deduce from that is that even if you set CONFIG_ACPI_PROCFS=y in
> the kernel configuration, this will have no impact at all.

About half a year ago I noticed that this Kconfig symbol is unused since
v2.6.38 [0]. As, apparently, nothing has changed it is currently unused
for over two and a half years.

I still don't really understand the purpose of this symbol. But whatever
it is, it might as well be dropped. If it's ever needed again it could
be re-added. Or, perhaps, an entirely different approach could be used
to accomplish what that symbol is supposed to do.


Paul Bolle

[0] http://marc.info/?l=linux-acpi&m=136398635322975

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