From: David Brownell <david-b@pacbell.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
linux-acpi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
huffcslists@gmail.com,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 8995] New: /proc/acpi/alarm worked; update to 2.6.22.2 and /sys/class/rtc/rtc0/wakealarm don't
Date: Mon, 5 Nov 2007 08:11:17 -0800 [thread overview]
Message-ID: <200711050811.18256.david-b@pacbell.net> (raw)
In-Reply-To: <200711042056.56763.rjw@sisk.pl>
On Sunday 04 November 2007, Rafael J. Wysocki wrote:
> On Sunday, 4 of November 2007, David Brownell wrote:
> >
> > So what's the status of this now ... are we back to having
> > the /sys/class/rtc/rtc0/wakealarm work with ACPI again
>
> Yes, it should work now.
A current git kernel seemed to work for me on at least one
system that had previously misbehaved ... both "standby" and
"disk" suspend now let the wakealarm do its thing. (And STR
has the usual unrelated framebuffer issues.) And I'm told
another person has seen it work again on his hardware. I'll
try it on a few other systems too, just to be sure.
Thanks for the bugfix, and update!
- Dave
prev parent reply other threads:[~2007-11-05 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8995-10286@http.bugzilla.kernel.org/>
2007-09-09 0:29 ` [Bugme-new] [Bug 8995] New: /proc/acpi/alarm worked; update to 2.6.22.2 and /sys/class/rtc/rtc0/wakealarm don't Andrew Morton
2007-09-09 11:32 ` Rafael J. Wysocki
2007-11-04 19:25 ` David Brownell
2007-11-04 19:56 ` Rafael J. Wysocki
[not found] ` <200711042056.56763.rjw@sisk.pl>
2007-11-05 16:11 ` David Brownell [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=200711050811.18256.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=huffcslists@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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