From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Lan Tianyu <lantianyu1986@gmail.com>, Len Brown <lenb@kernel.org>,
rjw@rjwysocki.net,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger kernel org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: remove unused ACPI_PROCFS Kconfig param
Date: Mon, 28 Oct 2013 09:42:51 +0100 [thread overview]
Message-ID: <526E238B.2070900@free-electrons.com> (raw)
In-Reply-To: <1382948855.32195.9.camel@x220.thuisdomein>
Hi Paul,
On 10/28/2013 09:27 AM, Paul Bolle wrote:
> 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
Good to know that nobody has complained about this for two and half
years :) This is then probably safe to remove this symbol for good.
Thanks again,
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
next prev parent reply other threads:[~2013-10-28 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 6:56 [PATCH] ACPI: remove unused ACPI_PROCFS Kconfig param Michael Opdenacker
2013-10-28 6:13 ` Lan Tianyu
2013-10-28 6:22 ` Michael Opdenacker
2013-10-28 8:27 ` Paul Bolle
2013-10-28 8:42 ` Michael Opdenacker [this message]
2013-10-29 5:51 ` Lan Tianyu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=526E238B.2070900@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=lantianyu1986@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox