public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull request] ACPI patches for 2.6.34-rc6
Date: Sat, 08 May 2010 01:19:43 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005080112300.5996@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1005071708010.901@i5.linux-foundation.org>

> On Sat, 8 May 2010, Rafael J. Wysocki wrote:
> > 
> > To calrify, I think the approach in the Matthew's patch is correct, but since I have
> > some bad experience with that particular thing, I prefer to make that change in
> > 2.6.35 and then move on to drop the flag entirely.
> 
> Oh,yes. I'm not suggesting we do it late in the -rc cycle. 
> 
> I just don't think the DMI table is a good idea, so in the longer run I 
> wan tto get rid of it, rather than have it grow (by quite a few entries, 
> in this case).
> 
> There are valid reasons for DMI tables in many cases, but in this case I 
> think the reason is simply that we do the wrong thing, so then we ended up 
> with a DMI table to "fix" the wrong thing we do.

Hi Linus,
Matthew, Rafael and I all agree with you on every aspect of this issue.

The DMI list is temporary.  Matthew's patch to do as you say
is already queued for 2.6.35.

I belive that Rafael was prudent in recommending we delay
the "real" fix until .35, as we discovered that the broken
machines suffered a 3-second delay on resume, polling for the SCI_EN
that the BIOS would never set, and so the proposed fix for that 
is queued for 2.6.35 as well.

thanks,
-Len

      reply	other threads:[~2010-05-08  5:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  2:22 [git pull request] ACPI patches for 2.6.34-rc6 Len Brown
2010-05-07  2:34 ` Linus Torvalds
2010-05-07  6:12   ` Matthew Garrett
2010-05-07 21:06     ` Linus Torvalds
2010-05-07 21:13       ` Matthew Garrett
2010-05-07 21:21         ` Linus Torvalds
2010-05-07 21:36           ` Matthew Garrett
2010-05-11 17:25             ` Matthew Garrett
2010-05-11 17:42               ` Linus Torvalds
2010-05-11 17:59                 ` Matthew Garrett
2010-05-11 18:17                   ` Linus Torvalds
2010-05-11 18:22                     ` Matthew Garrett
2010-05-12 16:07               ` Robert Wörle
2010-05-12 16:12                 ` Matthew Garrett
2010-05-07 22:39   ` Rafael J. Wysocki
2010-05-07 23:00     ` Linus Torvalds
2010-05-07 23:17       ` Rafael J. Wysocki
2010-05-07 23:21         ` Linus Torvalds
2010-05-08  0:03           ` Rafael J. Wysocki
2010-05-08  0:10             ` Linus Torvalds
2010-05-08  5:19               ` Len Brown [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=alpine.LFD.2.00.1005080112300.5996@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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