From: Lan Tianyu <tianyu.lan@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Sorin Manolache <sorinm@gmail.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-kernel@vger.kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: drivers/acpi/ac.c, re-enabling CONFIG_ACPI_PROCFS_POWER?
Date: Thu, 19 Jun 2014 14:32:40 +0800 [thread overview]
Message-ID: <53A28408.8040001@intel.com> (raw)
In-Reply-To: <1891948.UFv8RnVsZc@vostro.rjw.lan>
On 2014年06月19日 07:17, Rafael J. Wysocki wrote:
> On Wednesday, June 18, 2014 10:28:12 PM Sorin Manolache wrote:
>> Hello,
>>
>> Would it be worth considering re-enabling the old procfs interface for
>> ac.c? There are old tools still around (kpowersave from kde 3.5.10) that
>> expect /proc/acpi/ac_adapter.
>
> Can you please CC ACPI-related messages to linux-acpi@vger.kernel.org?
>
> I'm not sure how much effort that would require at this point. Rui, Tianyu?
I think we need to revert commit ab0fd67.
commit ab0fd674d6cef0904baa511f22613ef6474f8169
Author: Lan Tianyu <tianyu.lan@intel.com>
Date: Sat Oct 12 21:04:48 2013 +0800
ACPI / AC: Remove AC's proc directory.
AC's proc directory is not used and so remove it. Prepare for removing
/proc/acpi directory.
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Rafael
>
--
Best regards
Tianyu Lan
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-19 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53A1F65C.9090907@gmail.com>
2014-06-18 23:17 ` drivers/acpi/ac.c, re-enabling CONFIG_ACPI_PROCFS_POWER? Rafael J. Wysocki
2014-06-19 6:32 ` Lan Tianyu [this message]
2014-06-19 7:47 ` Lan Tianyu
2014-06-19 19:55 ` Sorin Manolache
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=53A28408.8040001@intel.com \
--to=tianyu.lan@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=sorinm@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).