public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
	bjorn.helgaas@hp.com, kimoto@lightlink.com, rjw@sisk.pl
Subject: Re: [patch for 2.6.32? 2/2] thinkpad-acpi: fix detection of old ThinkPads
Date: Fri, 20 Nov 2009 08:41:43 -0800	[thread overview]
Message-ID: <20091120084143.573258cd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091120120528.GB11107@khazad-dum.debian.net>

On Fri, 20 Nov 2009 10:05:28 -0200 Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:

> On Tue, 17 Nov 2009, akpm@linux-foundation.org wrote:
> > From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> > 
> > There is a problem in the quirk tables used by tpacpi_is_fw_known() and
> > tpacpi_check_outdated_fw(), which causes outdated BIOSes that are lacking
> > the EC firmware ID DMI field to never match.
> > 
> > This breaks module loading on, e.g.  a T23 with outdated BIOS, and the
> > module will refuse to load unless the "force_load=1" parameter is given.
> > 
> > Fix the quirk tables so that they can also match the outdated BIOSes,
> > which in turn will both fix the module loading, and also warn the user
> > that he is using outdated firmware and should upgrade.
> > 
> > This fixes a serious regression, introduced by commit
> > e675abafcc0df38125e6e94a9ba91c92fe774f52, "thinkpad-acpi: be more strict
> > when detecting a ThinkPad".
> > 
> > Addresses http://bugzilla.kernel.org/show_bug.cgi?id=14597
> > 
> > Reported-by: Paul Kimoto <kimoto@lightlink.com>
> > Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
> > Tested-by: Paul Kimoto <kimoto@lightlink.com>
> > Cc: Len Brown <lenb@kernel.org>
> > Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
> > Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> 
> This patch is not in -rc8.  Andrew, Len, can one of you please send it to
> Linus for merge in mainline?  It will hit enough users that I'd really
> prefer it to not wait for a -stable release.
> 

Yes, I'll send it in.

  reply	other threads:[~2009-11-20 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 22:07 [patch for 2.6.32? 2/2] thinkpad-acpi: fix detection of old ThinkPads akpm
2009-11-20 12:05 ` Henrique de Moraes Holschuh
2009-11-20 16:41   ` Andrew Morton [this message]
2009-11-25  5:41 ` 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=20091120084143.573258cd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=hmh@hmh.eng.br \
    --cc=kimoto@lightlink.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.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