linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm@lists.osdl.org, Zhang Rui <rui.zhang@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-pm@osdl.org, "linux-acpi@vger" <linux-acpi@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs	functions in sysfs
Date: Thu, 25 Jan 2007 13:08:13 +0100	[thread overview]
Message-ID: <20070125120813.GD23343@elf.ucw.cz> (raw)
In-Reply-To: <200701242128.14047.lenb@kernel.org>

On Wed 2007-01-24 21:28:13, Len Brown wrote:
> On Monday 08 January 2007 08:13, Pavel Machek wrote:
> > Hi!
> > 
> > > This patch set is against acpi-test sysfs branch which already converts
> > > ACPI to follow driver model. Now the ACPI procfs functions are
> > > duplicated in sysfs step by step. And I want the ACPI interface in sysfs
> > > works exactly the same way as in procfs.
> > 
> > No, you can't port same broken interface into sysfs. Some /proc
> > interfaces are horrible, and we do not want to create _exactly same_
> > horrible interfaces in /sys.
> 
> Please be specific.

/proc/acpi/alarm is horrible mess, as was detailed in another email
from David.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-01-25 12:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06 11:35 [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs Zhang Rui
2007-01-06 22:21 ` David Brownell
2007-01-07  5:54   ` [linux-pm] " Matthew Garrett
2007-01-08  3:31     ` David Brownell
2007-01-08 13:10       ` Pavel Machek
2007-01-25  4:14       ` Len Brown
2007-01-25  5:50         ` Matthew Garrett
2007-01-25  9:35         ` David Brownell
2007-01-08 11:40     ` Zhang Rui
2007-01-08 13:13       ` Pavel Machek
2007-01-25  2:28         ` Len Brown
2007-01-25 12:08           ` Pavel Machek [this message]
2007-01-25 13:15             ` David Brownell
2007-01-25 19:51               ` Pavel Machek
2007-01-26  1:36                 ` Zhang Rui
2007-01-10 20:53       ` David Brownell
2007-01-25  4:17         ` Len Brown
2007-01-25 13:15           ` Pavel Machek
2007-01-25  3:33     ` [linux-pm] " Len Brown
2007-01-25  3:28   ` Len Brown
2007-01-25  9:54     ` David Brownell
2007-01-25 19:37     ` Pavel Machek
2007-01-07 11:15 ` Pavel Machek
2007-01-25  2:03   ` Len Brown
2007-01-25  2:52     ` Nigel Cunningham
2007-01-25  8:17       ` Rafael J. Wysocki
2007-01-25 10:00         ` [linux-pm] " David Brownell
2007-01-18  6:53 ` Zhang Rui
2007-01-21  5:48 ` [PATCH 0/3] " Zhang Rui
2007-01-25  3:50   ` Len Brown

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=20070125120813.GD23343@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux-pm@osdl.org \
    --cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).