From: Pavel Machek <pavel@suse.cz>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Andrew Grover <andrew.grover@intel.com>,
ACPI mailing list <acpi-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] S4bios support for 2.5.63
Date: Tue, 4 Mar 2003 14:23:29 +0100 [thread overview]
Message-ID: <20030304132329.GF618@zaurus.ucw.cz> (raw)
In-Reply-To: <20030227141322.GV13404@poup.poupinou.org>
Hi!
> > +
> > + do {
> > + acpi_os_stall(1000);
> > + status = acpi_get_register (ACPI_BITREG_WAKE_STATUS, &in_value, ACPI_MTX_LOCK);
>
> Please use ACPI_MTX_DO_NOT_LOCK flags.
Is s/MTX_LOCK/MTX_DO_NOT_LOCK/
enough?
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-03-04 10:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 21:13 S4bios support for 2.5.63 Pavel Machek
2003-02-27 14:13 ` [ACPI] " Ducrot Bruno
2003-03-04 13:23 ` Pavel Machek [this message]
2003-03-04 12:00 ` Ducrot Bruno
2003-03-02 13:31 ` bert hubert
2003-03-02 18:44 ` Nigel Cunningham
2003-03-02 20:21 ` bert hubert
2003-03-02 22:22 ` Alan Cox
2003-03-03 0:39 ` Roger Luethi
2003-03-03 2:08 ` [ACPI] " Nigel Cunningham
2003-03-03 11:31 ` bert hubert
2003-03-03 12:17 ` Roger Luethi
2003-03-03 12:23 ` Pavel Machek
2003-03-03 12:35 ` bert hubert
2003-03-03 12:41 ` Pavel Machek
[not found] ` <1046700474.3782.197.camel@localhost>
2003-03-03 14:30 ` Roger Luethi
2003-03-03 22:06 ` Nigel Cunningham
2003-03-03 23:39 ` Roger Luethi
2003-03-04 0:36 ` Nigel Cunningham
2003-03-04 10:43 ` Roger Luethi
2003-03-04 9:12 ` bert hubert
2003-03-03 15:11 ` bert hubert
2003-03-03 16:40 ` Alan Cox
2003-03-03 16:23 ` P. Christeas
2003-03-03 16:28 ` bert hubert
2003-03-03 14:25 ` Alan Cox
2003-03-03 12:37 ` Roger Luethi
2003-03-03 14:09 ` Alan Cox
2003-03-03 14:37 ` [ACPI] " Ducrot Bruno
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=20030304132329.GF618@zaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=ducrot@poupinou.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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