stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Tunin <hanipouspilot@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH] ideapad_laptop: Lenovo G50-30 fix rfkill always reports wireless blocked
Date: Mon, 08 Dec 2014 20:53:40 +0300	[thread overview]
Message-ID: <5485E5A4.9070805@gmail.com> (raw)
In-Reply-To: <547753DE.9050809@gmail.com>

Is anything wrong with this patch?
It was made against last mainline kernel at the moment.
If a patch against linux-next needed, I can make it.
Without this patch wireless is always blocked.

Regards,

Dmitry.

27.11.2014 19:39, Dmitry Tunin пишет:
> Rfkill always shows wireless blocked unless ideapad_laptop is blacklisted.
> Add a quirk.
>
> Cc: stable@vger.kernel.org
> BugLink:https://bugs.launchpad.net/bugs/1397021
> Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
> ---
>   drivers/platform/x86/ideapad-laptop.c | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/drivers/platform/x86/ideapad-laptop.c b/drivers/platform/x86/ideapad-laptop.c
> index ed494f3..9958de6 100644
> --- a/drivers/platform/x86/ideapad-laptop.c
> +++ b/drivers/platform/x86/ideapad-laptop.c
> @@ -844,6 +844,13 @@ static const struct dmi_system_id no_hw_rfkill_list[] = {
>               DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo YOGA 3 Pro-1370"),
>           },
>       },
> +    {
> +        .ident = "Lenovo G50-30",
> +        .matches = {
> +            DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> +            DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo G50-30"),
> +        },
> +    },
>       {}
>   };
>

      reply	other threads:[~2014-12-08 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 16:39 [PATCH] ideapad_laptop: Lenovo G50-30 fix rfkill always reports wireless blocked Dmitry Tunin
2014-12-08 17:53 ` Dmitry Tunin [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=5485E5A4.9070805@gmail.com \
    --to=hanipouspilot@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).