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: <CANBuOYoJv5F=4H71fPoWx3MmzSQuKt_p5SPMJx1P=PGwDrEmPA@mail.gmail.com>
Date: Tue, 19 Aug 2025 15:19:17 +0200
From: Jihed Chaibi <jihed.chaibi.dev@...il.com>
To: Uwe Kleine-König <ukleinek@...nel.org>, 
	peter.ujfalusi@...il.com
Cc: linux-kernel@...r.kernel.org, dmitry.torokhov@...il.com, robh@...nel.org, 
	krzk+dt@...nel.org, lgirdwood@...il.com, tiwai@...e.com, conor+dt@...nel.org, 
	lee@...nel.org, broonie@...nel.org, gregkh@...uxfoundation.org, 
	linux-input@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-pwm@...r.kernel.org, linux-sound@...r.kernel.org, 
	linux-usb@...r.kernel.org, shuah@...nel.org
Subject: Re: [PATCH 0/8] dt-bindings: Convert TWL4030/6040 family binding to
 DT schema

> > The following eight patches are included in this series, covering the
> > audio, keypad, power, PWM, and USB sub-modules.
>
> Thanks for doing that.
>
> I think the patches are all orthogonal and can/should be applied by the
> respective subsystem maintainers once they are considered ready?
>

Hello Uwe, Peter, and everyone,

Thank you for the feedback, I am now working on a new v4 patch series
for each subsystem with few improvements and will make sure of their
orthogonality.

While working on this, I had a question about the 'maintainers:' property for
the new YAML bindings. I see from the MAINTAINERS file that Peter Ujfalusi
is the maintainer for the TWL4030 codec driver. I initially marked him as
maintainer for every new twl4030 related binding.

For those new YAML binding files I am creating, should I list only the driver
maintainer (Peter, once he confirms this), or should I add myself as
a co-maintainer since I am authoring these new binding files?

Pinging Peter for his thoughts on this as well.

Thanks again for your guidance.
Jihed

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ