lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 23 Jan 2016 07:57:23 -0500 From: Josh Boyer <jwboyer@...oraproject.org> To: Darren Hart <dvhart@...radead.org> Cc: Ike Panhc <ike.pan@...onical.com>, platform-driver-x86@...r.kernel.org, "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>, "stable@...r.kernel.org" <stable@...r.kernel.org> Subject: Re: [PATCH] ideapad-laptop: Add Lenovo Yoga 700 to no_hw_rfkill dmi list On Sat, Jan 23, 2016 at 2:27 AM, Darren Hart <dvhart@...radead.org> wrote: > On Mon, Jan 18, 2016 at 02:32:53PM -0500, Josh Boyer wrote: >> Like the Yoga 900 models the Lenovo Yoga 700 does not have a >> hw rfkill switch, and trying to read the hw rfkill switch through the >> ideapad module causes it to always reported blocking breaking wifi. >> >> This commit adds the Lenovo Yoga 700 to the no_hw_rfkill dmi list, fixing >> the wifi breakage. >> >> BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1295272 >> Tested-by: <dinyar.rabady+spam@...il.com> >> Cc: stable@...r.kernel.org >> Signed-off-by: Josh Boyer <jwboyer@...oraproject.org> >> --- >> >> This applies to the for-next branch of the platform-x86-drivers tree >> >> >> 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 d28db0e793df..51178626305d 100644 >> --- a/drivers/platform/x86/ideapad-laptop.c >> +++ b/drivers/platform/x86/ideapad-laptop.c >> @@ -900,6 +900,13 @@ static const struct dmi_system_id no_hw_rfkill_list[] = { >> }, >> }, >> { >> + .ident = "Lenogo Yoga 700", > > Josh, > > Is this a typo? "Lenogo"? Please tell me it's a typo.... :-) Ugh, yes. A typo. One that apparently doesn't matter in functionality because the tester used this exact patch and things work, but embarrassing either way. Do you need me to send a v2, or is that something you can fixup? josh
Powered by blists - more mailing lists