[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <05539224-6207-4dfa-a4e2-99947ec1fc62@roeck-us.net>
Date: Thu, 31 Jul 2025 05:53:54 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Antheas Kapenekakis <lkml@...heas.dev>,
Cryolitia PukNgae <liziyao@...ontech.com>
Cc: Cryolitia@...il.com, Jean Delvare <jdelvare@...e.com>,
Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
linux-hwmon@...r.kernel.org, linux-doc@...r.kernel.org,
Celeste Liu <CoelacanthusHex@...il.com>, Yao Zi <ziyao@...root.org>,
Derek John Clark <derekjohn.clark@...il.com>,
Marcin StrÄ…gowski <marcin@...agowski.com>,
someone5678 <someone5678.dev@...il.com>,
Justin Weiss <justin@...tinweiss.com>, command_block <mtf@...me>
Subject: Re: [PATCH v6 1/2] hwmon: add GPD devices sensor driver
On 7/31/25 01:13, Antheas Kapenekakis wrote:
> On Thu, 31 Jul 2025 at 05:30, Cryolitia PukNgae <liziyao@...ontech.com> wrote:
>>
>> Personally, I'd prefer to maintain this small driver in the hwmon
>> subsystem until we need to write drivers for the same EC with more
>> diverse subsystem functionality. We can then discuss and learn how to
>> evolve it. I personally don't think that's going to happen in the near
>> future.
>>
>> So, could we continue reviewing the current patch series? Where are we
>> stuck?
>
> Either is fine by me. The move is simply a rename anyway. My reasoning
> was it will take a bit of back and forth to get approved and charge
> limiting is a standard feature now on all manufacturers except GPD, so
> I expect them to add it soon. But since it is a rename, it is not a
> blocker for reviewing in any case.
>
It is moving code from one maintainer domain to another. That is like moving
from one country to another. It is not "just" a rename.
Guenter
Powered by blists - more mailing lists