From: Andi Kleen <andi@firstfloor.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: linux acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Andi Kleen <andi@firstfloor.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Holger Macht <hmacht@suse.de>, mjg59 <mjg59@srcf.ucam.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: [patch 1/11]avoid check _STA method
Date: Wed, 27 Aug 2008 09:53:09 +0200 [thread overview]
Message-ID: <20080827075309.GP26610@one.firstfloor.org> (raw)
In-Reply-To: <1219806859.32665.57.camel@sli10-desk.sh.intel.com>
On Wed, Aug 27, 2008 at 11:14:19AM +0800, Shaohua Li wrote:
> In some BIOSes, every _STA method call will send a notification again,
> this cause freeze. And in some BIOSes, it appears _STA should be called
> after _DCK. This tries to avoid calls _STA, and still keep the device
> present check.
> http://bugzilla.kernel.org/show_bug.cgi?id=10431
General comment before I review any code. Your mailer adds strange
characters to the comment log: (e.g. in this case before the "In"
and the "http"). My vim displays that as lots of &&&&&? Can you
remove that please?
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-08-27 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 3:14 [patch 1/11]avoid check _STA method Shaohua Li
2008-08-27 7:53 ` Andi Kleen [this message]
2008-08-27 8:24 ` Li, Shaohua
2008-08-27 8:56 ` Andi Kleen
2008-08-27 8:57 ` Alan Jenkins
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 2:02 Shaohua Li
2008-08-29 15:19 ` Thomas Renninger
2008-09-22 10:57 ` Holger Macht
2008-09-24 2:51 ` Shaohua Li
2008-09-24 12:17 ` Holger Macht
2008-09-25 14:49 ` Holger Macht
2008-09-26 1:04 ` Shaohua Li
2008-11-11 12:17 ` Holger Macht
2008-09-24 3:38 ` 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=20080827075309.GP26610@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=hmacht@suse.de \
--cc=hmh@hmh.eng.br \
--cc=htejun@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=shaohua.li@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