linux-kernel - Re: [PATCH 2/3] hwmon: (nct6775) Implement custom lock by ACPI mutex.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <b7616187-87d8-c87f-8f66-d5936a33395f@roeck-us.net>
Date:   Thu, 25 Nov 2021 11:54:11 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Eugene Shalygin <eugene.shalygin@...il.com>,
        Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Denis Pauk <pauk.denis@...il.com>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        thomas@...ssschuh.net, Jean Delvare <jdelvare@...e.com>,
        linux-hwmon@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] hwmon: (nct6775) Implement custom lock by ACPI mutex.

On 11/25/21 6:00 AM, Eugene Shalygin wrote:
>> Please, do not top post in the mailing lists!
> 
> Well, it was almost a new topic...
> 
>> I'm not sure I have got the above correctly, do you mean that the just
>> submitted asus_wmi_sensors HWMON driver will be replaced by your
>> changes? If so, you guys, need a lot to improve communication between
>> each other before submitting anything upstream.
> 
> Yes, you get it right. Sorry for that, it was a long story and I
> worked on the subject
> only occasionally, so that when Denis took the code and submitted it
> to the mainline
> I was not sure which approach is better, and so I did not stop him.
> 

We won't be heving two drivers with the same functionality. Give me one
reason why I should not drop the wmi driver (or both of them; I am not
sure which one we are talking about here).

On top of all that, this submission isn't about any of the wmi drivers,
but for the nct6775 driver, which just adds to the confusion.

Guenter