linux-kernel - Re: drivers/acpi/ac.c, re-enabling CONFIG_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 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]

Date:	Thu, 19 Jun 2014 14:32:40 +0800
From:	Lan Tianyu <tianyu.lan@...el.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
CC:	Sorin Manolache <sorinm@...il.com>,
	Zhang Rui <rui.zhang@...el.com>, linux-kernel@...r.kernel.org,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: drivers/acpi/ac.c, re-enabling CONFIG_ACPI_PROCFS_POWER?

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@...r.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@...el.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@...el.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>


> 
> Rafael
> 


-- 
Best regards
Tianyu Lan
--
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/