All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: platform-driver-x86@vger.kernel.org
Cc: Azael Avalos <coproscefalo@gmail.com>,
	Seth Forshee <seth.forshee@canonical.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Darren Hart <dvhart@infradead.org>
Subject: Re: [PATCH] [RESEND 2] toshiba_acpi: Add missing ID (TOS6207)
Date: Fri, 28 Nov 2014 19:44:10 +0100	[thread overview]
Message-ID: <201411281944.11309.linux@rainbow-software.org> (raw)
In-Reply-To: <1417165432-21691-1-git-send-email-linux@rainbow-software.org>

cc: Darren Hart

On Friday 28 November 2014 10:03:52 Ondrej Zary wrote:
> toshiba_acpi was always missing TOS6207 ID so it did not load automatically
> on some laptops (such as Portege R100). But it worked fine if loaded
> manually. Commit 135740de7764 ("toshiba_acpi: Convert to use acpi_driver")
> broke that and the driver does not work even when loaded manually since
> then.
>
> Add TOS6207 ID to fix it.
>
> Tested on Toshiba Portege R100.
>
> Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> ---
>  drivers/platform/x86/toshiba_acpi.c |    1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/toshiba_acpi.c
> b/drivers/platform/x86/toshiba_acpi.c index ab6151f..0ce2129 100644
> --- a/drivers/platform/x86/toshiba_acpi.c
> +++ b/drivers/platform/x86/toshiba_acpi.c
> @@ -186,6 +186,7 @@ static struct toshiba_acpi_dev *toshiba_acpi;
>
>  static const struct acpi_device_id toshiba_device_ids[] = {
>  	{"TOS6200", 0},
> +	{"TOS6207", 0},
>  	{"TOS6208", 0},
>  	{"TOS1900", 0},
>  	{"", 0},


-- 
Ondrej Zary

      reply	other threads:[~2014-11-28 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28  9:03 [PATCH] [RESEND 2] toshiba_acpi: Add missing ID (TOS6207) Ondrej Zary
2014-11-28 18:44 ` Ondrej Zary [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=201411281944.11309.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=coproscefalo@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.