From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops
Date: Wed, 14 Aug 2013 09:38:36 -0700 [thread overview]
Message-ID: <20130814093836.57002b77@jbarnes-desktop> (raw)
In-Reply-To: <d4635f76028172e872cc4be506bad1c11816f75a.1376494861.git.joseph.salisbury@canonical.com>
On Wed, 14 Aug 2013 12:22:49 -0400
Joseph Salisbury <joseph.salisbury@canonical.com> wrote:
> BugLink: http://bugs.launchpad.net/bugs/1210848
>
> On an ASUSTek G60JX laptop, the intel_ips driver spams the log with a warning message: "ME failed to update for more than 1s, likely hung". This ME doesn't support the feature, so requesting it be blacklisted for now.
>
> Signed-off-by: Joseph Salisbury <joseph.salisbury@canonical.com>
> Tested-by: Nick Jenkins <tech.crew.jenkins@gmail.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Cc: platform-driver-x86@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Cc: stable@vger.kernel.org
> ---
> drivers/platform/x86/intel_ips.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
> index 18dcb58..6d8c5e0 100644
> --- a/drivers/platform/x86/intel_ips.c
> +++ b/drivers/platform/x86/intel_ips.c
> @@ -1501,6 +1501,14 @@ static const struct dmi_system_id ips_blacklist[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "HP ProBook"),
> },
> },
> + {
> + .callback = ips_blacklist_callback,
> + .ident = "G60JX",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK Computer Inc."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "G60JX"),
> + },
> + },
> { } /* terminating entry */
> };
>
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Linus, you may want to pick this up directly, as I'm not sure if
Matthew is still looking after the x86 drivers these days.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-08-14 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1376494861.git.joseph.salisbury@canonical.com>
2013-08-14 16:22 ` [PATCH 1/1] intel_ips: blacklist ASUSTek G60JX laptops Joseph Salisbury
2013-08-14 16:38 ` Jesse Barnes [this message]
2013-08-14 16:54 ` Matthew Garrett
2013-08-14 21:11 ` Linus Torvalds
2013-08-29 16:18 ` Joseph Salisbury
2013-08-29 16:32 ` Jesse Barnes
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=20130814093836.57002b77@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--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