Messages in this thread | | | From | Andy Shevchenko <> | Date | Thu, 25 Nov 2021 15:51:38 +0200 | Subject | Re: [PATCH 2/3] hwmon: (nct6775) Implement custom lock by ACPI mutex. |
| |
On Thu, Nov 25, 2021 at 3:15 PM Eugene Shalygin <eugene.shalygin@gmail.com> wrote: > > Dear Andy, Denis, and Günter,
Please, do not top post in the mailing lists!
> Denis worked on my code with the first attempt to read EC sensors from > ASUS motherboards and submitted it as a driver named > "asus_wmi_ec_sensors", which is not in hwmon-next. Now he adds the > ACPI lock feature to support other motherboards, and I have another > iteration of the EC sensor driver under development (needs some > polishment) that utilizes the same concept (ACPI lock instead of WMI > methods), which is smaller, cleaner and faster than the WMI-based one. > I'm going to submit it to the mainline too. I think it should replace > the WMI one. In anticipation of that, can we change the name of the > accepted driver (asus_wmi_ec_sensors -> asus_ec_sensors) now, in order > to not confuse users in the next version and to remove implementation > detail from the module name? The drivers provide indistinguishable > data to HWMON.
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.
-- With Best Regards, Andy Shevchenko
| |