linux-kernel - Re: [PATCH v2 1/1] dt-bindings: hwmon/regulator: Convert ltc2978.txt to yaml

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] [day] [month] [year] [list]

Message-ID: <22f0484c-52da-4845-9c6a-8041d424d775@roeck-us.net>
Date: Sun, 25 Aug 2024 16:03:04 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Frank Li <Frank.li@....com>
Cc: Mark Brown <broonie@...nel.org>, Jean Delvare <jdelvare@...e.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
 "open list:HARDWARE MONITORING" <linux-hwmon@...r.kernel.org>,
 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
 <devicetree@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>,
 imx@...ts.linux.dev
Subject: Re: [PATCH v2 1/1] dt-bindings: hwmon/regulator: Convert ltc2978.txt
 to yaml

On 8/19/24 14:45, Frank Li wrote:
> On Mon, Aug 19, 2024 at 02:37:00PM -0700, Guenter Roeck wrote:
>> On Mon, Aug 19, 2024 at 03:39:38PM -0400, Frank Li wrote:
>>> On Mon, Aug 19, 2024 at 08:11:46PM +0100, Mark Brown wrote:
>>>> On Mon, Aug 19, 2024 at 03:06:51PM -0400, Frank Li wrote:
>>>>
>>>>> change from v1 to v2
>>>>> - maintainer change to Mark Brown <broonie@...nel.org> (regulator maintainer)
>>>>
>>>> I also shouldn't be the maintainer for this specific binding, it should
>>>> be someone with knowledge of the devices.  This is a requirement imposed
>>>> by the DT people, I'd be happy to just not list a specific maintainer.
>>>
>>> I remember 'maintainer' is required property for yaml.
>>> Look like Guenter Roeck contribute many code for this driver.
>>>
>>
>> Yes, but I do not maintain code or documentation outside the hardware
>> monitoring or watchdog subsystems. You want this file attached to the
>> regulator subsystem, so you'll have to find a maintainer from that
>> subsystem or sign up to maintain it yourself.
> 
> How about just leave in origial place? I think you are more familar than
> me about this controller!
> 

I really do not want to be involved in this discussion any further.
You insisted in moving the file, so you should be willing to bear
the consequences (meaning: add yourself as maintainer), or at least
find someone who does. Please keep in mind that the maintainer will have
to coordinate future patch series if changes to both the devicetree
property descriptions and to the driver are needed.

Guenter