From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Stefan Seyfried" <seife@suse.de>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
Henne <henne@nachtwindheim.de>,
"Arjan van de Ven" <arjan@infradead.org>,
"Brown, Len" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][BUTTON] remove procfs-interface
Date: Mon, 16 Jul 2007 13:17:27 +0530 [thread overview]
Message-ID: <a781481a0707160047i59b45797y491e9b303d2d8909@mail.gmail.com> (raw)
In-Reply-To: <20070716073533.GA23083@suse.de>
On 7/16/07, Stefan Seyfried <seife@suse.de> wrote:
> Holy sh*t. There is not even a functional replacement ready, but still
> everybody wants to remove /proc/acpi. (Maybe the replacement started
> to work recently, i have not looked into this area for the last months.
> This does not change my pint, though).
> This is not going to work.
> IMNSHO, we need the new interface available and usable for quite some time
> (i'd say for over one year), and then we can start to phase out the old
> interface.
> Starting with removing /proc/acpi is not the correct ordering of actions.
Heh, you're 3 days late to the party, but yeah, Zhang's corrected me/
pointed this out (the functionality in /proc/acpi not yet in the sysfs I/F
being used by said userspace tools) already. I guess I had originally
misunderstood the "some user space tools still use the ACPI procfs" bit.
Satyam
prev parent reply other threads:[~2007-07-16 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 8:58 [PATCH][ACPI][BUTTON] " Henne
2007-07-12 9:00 ` Arjan van de Ven
2007-07-12 9:40 ` Henne
2007-07-12 9:46 ` Zhang, Rui
2007-07-12 10:26 ` Richard Hughes
2007-07-12 14:38 ` Brown, Len
2007-07-12 19:07 ` Satyam Sharma
2007-07-13 7:23 ` Zhang Rui
2007-07-16 7:35 ` [PATCH][BUTTON] " Stefan Seyfried
2007-07-16 7:47 ` Satyam Sharma [this message]
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=a781481a0707160047i59b45797y491e9b303d2d8909@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=henne@nachtwindheim.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=seife@suse.de \
/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
all inboxes | Powered by JetHome®