public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Rui" <rui.zhang@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: "Németh Márton" <nm127@freemail.hu>,
	trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards
Date: Wed, 12 Mar 2008 15:12:25 +0800	[thread overview]
Message-ID: <1205305945.2240.56.camel@acpi-hp-zz.sh.intel.com> (raw)
In-Reply-To: <1205300688.2240.47.camel@acpi-hp-zz.sh.intel.com>


On Wed, 2008-03-12 at 13:44 +0800, Zhang, Rui wrote:
> On Wed, 2008-03-12 at 13:40 +0800, Len Brown wrote:
> > Actually,
> > This case (and others)
> > seems to be taken care of by Rui's recent patch for 8544, yes?
> > 
> >  [PATCH] ACPI: thermal fixup for broken BIOS which has invalid trip
> > points
> Hah, it doesn't cover the active trip point.
> 
> Please review this patch. :)
After reading the ACPI spec again, 
"If _PSV is defined then either _PSL or _TZD must be defined. _PSL and
_TZD may both be defined".
"_TZD is optional outside of the _PSV requirement".
which means that we should not throw out an error without checking the
_TZD method.
I think the patch still doesn't make sense, please ignore this patch and
wait for the refreshed patch.. :)

thanks,
rui


  reply	other threads:[~2008-03-12  7:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  0:06 [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards Thomas Renninger
2008-03-12  4:10 ` Len Brown
2008-03-12  5:40   ` Len Brown
2008-03-12  5:44     ` Zhang, Rui
2008-03-12  7:12       ` Zhang, Rui [this message]
2008-03-13  7:03         ` Zhang, Rui
2008-03-13 21:15           ` Németh Márton
2008-03-30  0:43             ` Yinghai Lu
2008-03-31  5:55               ` Németh Márton

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=1205305945.2240.56.camel@acpi-hp-zz.sh.intel.com \
    --to=rui.zhang@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=nm127@freemail.hu \
    --cc=trenn@suse.de \
    /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