From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216468] hp_wmi: HP Elitebook 865 G9 after update BIOS to version U82 01.02.01 Rev.A causing rfkill soft blocked wifi
Date: Thu, 27 Oct 2022 15:51:11 +0000 [thread overview]
Message-ID: <bug-216468-215701-qZVeZEhnIW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216468-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216468
--- Comment #8 from jorge.lopez2@hp.com ---
Ok, I will take a look.
Regards,
Jorge Lopez
Hewlett-Packard
"Once you stop learning, you start dying"
Albert Einstein
From: Limonciello, Mario <Mario.Limonciello@amd.com>
Sent: Thursday, October 27, 2022 10:27 AM
To: bugzilla-daemon@kernel.org; platform-driver-x86@vger.kernel.org; Lopez,
Jorge A (Security) <jorge.lopez2@hp.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: RE: [Bug 216468] hp_wmi: HP Elitebook 865 G9 after update BIOS to
version U82 01.02.01 Rev.A causing rfkill soft blocked wifi
CAUTION: External Email
[Public]
+Jorge,
Can you take a look at this?
Something that comes to mind to me is maybe the more modern
platforms shouldn't be using hp_wmi's RFKILL feature anymore.
Aren't there rfkill services provided by all modern wifi drivers now?
> -----Original Message-----
> From: bugzilla-daemon@kernel.org<mailto:bugzilla-daemon@kernel.org>
> <bugzilla-daemon@kernel.org<mailto:bugzilla-daemon@kernel.org>>
> Sent: Thursday, October 27, 2022 09:58
> To:
> platform-driver-x86@vger.kernel.org<mailto:platform-driver-x86@vger.kernel.org>
> Subject: [Bug 216468] hp_wmi: HP Elitebook 865 G9 after update BIOS to
> version U82 01.02.01 Rev.A causing rfkill soft blocked wifi
>
>
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugz<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugz>
>
> illa.kernel.org%2Fshow_bug.cgi%3Fid%3D216468<http://illa.kernel.org%2Fshow_bug.cgi%3Fid%3D216468>
> &data=05%7C01%7Cm
> ario.limonciello%40amd.com%7C01a1b92da9704ede465f08dab82bbf27%7C3d
> d8961fe4884e608e11a82d994e183d%7C0%7C0%7C638024795272794223%7CU
> nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZVHHH70%2
> FoyrXWVbad9GvomwvlYaGwhpdQEiGEXJNFcg%3D&reserved=0
>
> Mario Limonciello (AMD)
> (mario.limonciello@amd.com<mailto:mario.limonciello@amd.com>) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Component|Platform |Platform_x86
> Assignee|drivers_platform@kernel-bug
> |drivers_platform_x86@kernel
> |s.osdl.org |-bugs.osdl.org
>
> --
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-10-27 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216468-215701@https.bugzilla.kernel.org/>
2022-10-27 14:58 ` [Bug 216468] hp_wmi: HP Elitebook 865 G9 after update BIOS to version U82 01.02.01 Rev.A causing rfkill soft blocked wifi bugzilla-daemon
2022-10-27 15:27 ` Limonciello, Mario
2022-10-27 15:27 ` bugzilla-daemon
2022-10-27 15:51 ` bugzilla-daemon [this message]
2022-10-28 16:10 ` bugzilla-daemon
2022-11-07 13:20 ` bugzilla-daemon
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=bug-216468-215701-qZVeZEhnIW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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