From: Len Brown <lenb@kernel.org>
To: Anisse Astier <anisse@astier.eu>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 16/16] ACPI: add DMI entry to work around another insane Toshiba BIOS
Date: Wed, 29 Sep 2010 13:38:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1009291330390.3855@localhost.localdomain> (raw)
In-Reply-To: <20100929115108.1c596067@destiny.ordissimo>
> If you prefer that I open tickets on bugzilla to process this kind of
> bug, please let me know.
e-mail is normally fastest, but it can be lossy for me,
particularly during summer vacation or when i'm traveling
to a conference for a week. I fully intend to catch up
when i return, but rarely succeed in doing so.
bugzilla never forgets, and last night I scanned through
all the "RESOLVED" ACPI bugs (bugs with patches), which
is why I happened to see the other models before yours.
But I see it now, so you need do nothing more.
Acutally, if you can verify that if you modify the
entry to DMI_MATCH(DMI_PRODUCT_NAME, "Satellite");
that it still works on your Toshiba, that would be great.
Because that is the path forward that seems to make
most sense right now.
thanks,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-09-29 17:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 3:44 ACPI patches for 2.6.36-rc6 Len Brown
2010-09-29 3:44 ` [PATCH 01/16] ACPI: Don't report current_now if battery reports in mWh Len Brown
2010-09-29 3:44 ` [PATCH 02/16] PM / ACPI: Blacklist systems known to require acpi_sleep=nonvs Len Brown
2010-09-29 3:44 ` [PATCH 03/16] ACPI: enable repeated PCIEXP wakeup by clearing PCIEXP_WAKE_STS on resume Len Brown
2010-09-29 3:44 ` [PATCH 04/16] ACPI: delete ZEPTO idle=nomwait DMI quirk Len Brown
2010-09-29 3:44 ` [PATCH 05/16] ACPI: expand Vista blacklist to include SP1 and SP2 Len Brown
2010-09-29 3:44 ` [PATCH 06/16] ACPI: EC: add Vista incompatibility DMI entry for Toshiba Satellite L355 Len Brown
2010-09-29 3:44 ` [PATCH 07/16] ACPI: fix build warnings resulting from merge window conflict Len Brown
2010-09-29 3:44 ` [PATCH 08/16] ACPI video: fix a poor warning message Len Brown
2010-09-29 3:44 ` [PATCH 09/16] ACPI: Fix typos Len Brown
2010-09-29 3:44 ` [PATCH 10/16] ACPI: add missing __percpu markup in arch/x86/kernel/acpi/cstate.c Len Brown
2010-09-29 3:44 ` [PATCH 11/16] ACPI: Kconfig: fix typo Len Brown
2010-09-29 3:44 ` [PATCH 12/16] ACPI: Fix the ERST build warning Len Brown
2010-09-29 18:09 ` Len Brown
2010-09-29 3:44 ` [PATCH 13/16] ACPI: acpi_pad: simplify code to avoid false gcc " Len Brown
2010-09-29 3:44 ` [PATCH 14/16] ACPI: fan: Fix more unbalanced code block Len Brown
2010-09-29 3:44 ` [PATCH 15/16] ACPI: Disable Windows Vista compatibility for Toshiba P305D Len Brown
2010-09-29 3:44 ` [PATCH 16/16] ACPI: add DMI entry to work around another insane Toshiba BIOS Len Brown
2010-09-29 9:51 ` Anisse Astier
2010-09-29 17:38 ` Len Brown [this message]
2010-09-29 18:32 ` [PATCH] ACPI: invoke DSDT corruption workaround on all Toshiba Satellite Len Brown
2010-09-30 13:27 ` Anisse Astier
2010-10-02 2:54 ` Len Brown
2010-09-29 15:48 ` [PATCH 16/16] ACPI: add DMI entry to work around another insane Toshiba BIOS Matthew Garrett
2010-09-29 17:27 ` Len Brown
2010-09-29 17:32 ` Matthew Garrett
2010-09-29 17:53 ` 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=alpine.LFD.2.00.1009291330390.3855@localhost.localdomain \
--to=lenb@kernel.org \
--cc=anisse@astier.eu \
--cc=linux-acpi@vger.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