linux-kernel - RE: [PATCH 0/5] platform/x86: intel-vbtn: Fixes + rework to make it work on more devices

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e729ee1142a94fd394e0dbfb84e52a4b@AUSX13MPC101.AMER.DELL.COM>
Date:   Mon, 4 May 2020 15:38:58 +0000
From:   <Mario.Limonciello@...l.com>
To:     <hdegoede@...hat.com>, <dvhart@...radead.org>, <andy@...radead.org>
CC:     <linux-acpi@...r.kernel.org>,
        <platform-driver-x86@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/5] platform/x86: intel-vbtn: Fixes + rework to make it
 work on more devices

> -----Original Message-----
> From: Hans de Goede <hdegoede@...hat.com>
> Sent: Saturday, May 2, 2020 1:30 PM
> To: Darren Hart; Andy Shevchenko; Limonciello, Mario
> Cc: Hans de Goede; linux-acpi@...r.kernel.org; platform-driver-
> x86@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: [PATCH 0/5] platform/x86: intel-vbtn: Fixes + rework to make it work
> on more devices
> 
> 
> [EXTERNAL EMAIL]
> 
> Hi All,
> 
> Here is a series of fixes, mostly aimed at fixing commit: de9647efeaa9
> ("platform/x86: intel-vbtn: Only activate tablet mode switch on 2-in-1's")
> causing the driver to not bind on some devices where it could and
> should report SW_TABLET_MODE.
> 
> The last commit makes the driver also work on some devices where it
> previously would not work because they lack a VBDL method.
> 
> Mario, can you test this on a Dell XPS 9360 (for which you wrote the
> de9647efeaa9 commit) to ensure that this series does not cause a
> regression there?

Unfortunately I can't double check that with WFH, I don't have access to this hardware.

> Also I have a question for you about using the DMI
> chassis-type for this / a proposal for dealing with this differently
> below the '---' of the commit msg of the 4th patch.


OK will look.