linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Jerone Young <jerone.young@canonical.com>,
	Alex Chiang <achiang@canonical.com>,
	lenb@kernel.org, colin.king@canonical.com,
	linux-acpi@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	stable@kernel.org
Subject: Re: [PATCH] ACPI: DMI init_set_sci_en_on_resume for multiple Lenovo ThinkPads
Date: Tue, 20 Apr 2010 21:01:10 +0200	[thread overview]
Message-ID: <201004202101.10245.rjw@sisk.pl> (raw)
In-Reply-To: <20100420172419.GA9719@srcf.ucam.org>

On Tuesday 20 April 2010, Matthew Garrett wrote:
> On Tue, Apr 20, 2010 at 12:18:56PM -0500, Jerone Young wrote:
> 
> > I could agree, but the only issue is if you go to the thinkpad-acpi or
> > ibm-acpi mailing list they would probably disagree as there have been
> > updates to the bios in the past required for proper functionality of
> > Thinkpads ;-) .. the bios update methods have not changed since then for
> > Thinkpads.
> 
> If another OS works, and if Linux can be made to work without impairing 
> the functionality of working machines, then Linux should be made to 
> work. Always. Updating the BIOS should be limited to cases where it's 
> impossible to fix things up in the OS.

Agreed.

Rafael

  reply	other threads:[~2010-04-20 19:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 14:03 [PATCH] ACPI: DMI init_set_sci_en_on_resume for multiple Lenovo ThinkPads Alex Chiang
2010-04-20 14:46 ` Matthew Garrett
2010-04-20 14:54   ` Alex Chiang
2010-04-20 16:56 ` Jerone Young
2010-04-20 17:14   ` Matthew Garrett
2010-04-20 17:18     ` Jerone Young
2010-04-20 17:24       ` Matthew Garrett
2010-04-20 19:01         ` Rafael J. Wysocki [this message]
2010-04-20 17:20   ` Alex Chiang
2010-04-22 20:41 ` Alex Chiang
2010-05-05 20:34 ` Len Brown
2010-05-05 22:42   ` Alex Chiang

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=201004202101.10245.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=achiang@canonical.com \
    --cc=colin.king@canonical.com \
    --cc=jerone.young@canonical.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=stable@kernel.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;
as well as URLs for NNTP newsgroup(s).