From: Thomas Renninger <trenn@suse.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: Remove last acpi procfs dirs after being marked deprecated for a decade
Date: Wed, 27 May 2020 18:07:25 +0200 [thread overview]
Message-ID: <5786623.y7pTLF2AKN@c100> (raw)
In-Reply-To: <CAJZ5v0hAYRb9gZ8s=bZQ1NQrm5uUk5eLhLMwj2+pR2Apmd+WfA@mail.gmail.com>
Am Mittwoch, 27. Mai 2020, 17:49:09 CEST schrieb Rafael J. Wysocki:
> On Wed, May 27, 2020 at 5:33 PM Thomas Renninger <trenn@suse.de> wrote:
> > Kernel development should not be hindered anymore by this absolutely
> > outdated stuff.
>
> Well, this is a bit vague.
>
> I'm not against making this change, but why do it now? Is there
> anything in particular that cannot be done without it?
Because of the deprecated message being shown on laptops booting with
the option enabled. I got a bugreport about it recently.
I could not please check_patch to properly include this commit id
(recon the double quotes in the title):
e63f6e28dda6de3de2392ddca321e211fd860925
Date: Mon Jul 7 01:13:46 2014 +0200
Revert "ACPI / AC: Remove AC's proc directory."
Revert commit ab0fd674d6ce (ACPI / AC: Remove AC's proc directory.),
because some old tools (e.g. kpowersave from kde 3.5.10) are still
using /proc/acpi/ac_adapter.
Fixes: ab0fd674d6ce (ACPI / AC: Remove AC's proc directory.)
kpowersave was written by myself and I can say for sure, that this stuff
is more than outdated.
Thanks,
Thomas
next prev parent reply other threads:[~2020-05-27 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 15:33 Remove last acpi procfs dirs after being marked deprecated for a decade Thomas Renninger
2020-05-27 15:49 ` Rafael J. Wysocki
2020-05-27 16:07 ` Thomas Renninger [this message]
2020-05-27 17:46 ` Rafael J. Wysocki
2020-06-22 15:45 ` Rafael J. Wysocki
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=5786623.y7pTLF2AKN@c100 \
--to=trenn@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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