From: Len Brown <lenb@kernel.org>
To: David Brownell <david-b@pacbell.net>
Cc: Zhang Rui <rui.zhang@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-pm@lists.osdl.org,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
linux-pm@osdl.org
Subject: Re: [linux-pm] [PATCH 0/6] [-mm]: ACPI: duplicate ACPI procfs functions in sysfs
Date: Wed, 24 Jan 2007 23:17:48 -0500 [thread overview]
Message-ID: <200701242317.48273.lenb@kernel.org> (raw)
In-Reply-To: <200701101253.28151.david-b@pacbell.net>
On Wednesday 10 January 2007 15:53, David Brownell wrote:
> On Monday 08 January 2007 3:40 am, Zhang Rui wrote:
> >
> > if /sys/class/rtc/rtcN/alarm can provide the same function, it's great
> > and I'll drop patch#03. I'll also mark /proc/acpi/alarm as deprecated if
> > David's patches are merged. :)
>
> One help there would be someone from the ACPI team signing off on
> patch #3 of the series I sent, which teaches ACPI how to export the
> extra registers to the rtc-cmos driver.
done.
> There will be another ACPI patch at some point, actually kicking
> in hooks needed to handle system wakeup, but getting the PC into
> the RTC class framework is an important first step.
>
> Once there's a proper replacement for /proc/acpi/alarm it becomes
> a candidate for removal. Maybe sooner rather than later, unless
> some users for that old file turn up...
Sometimes that file's syntax is useful -- wake up at 7:00,
but those testing suspend-resume want to wake up 1 minute in the future
now mater what time it is...
next prev parent reply other threads:[~2007-01-25 4:19 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
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 [this message]
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=200701242317.48273.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=david-b@pacbell.net \
--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).