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] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c83e4d5-7192-4e02-baba-381bece513c2@linaro.org>
Date: Tue, 12 Aug 2025 10:26:20 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
 Vikash Garodia <quic_vgarodia@...cinc.com>,
 Dikshita Agarwal <quic_dikshita@...cinc.com>,
 Abhinav Kumar <abhinav.kumar@...ux.dev>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, linux-media@...r.kernel.org,
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [PATCH] media: iris: MAINTAINERS: Document actual maintainership
 by Bryan O'Donoghue

On 15/07/2025 13:03, Bryan O'Donoghue wrote:
>>>
>>> Reading too much? Bryan HANDLES THE PATCHES.
>>>
>>> That's it.
>>>
>>> There is nothing "too much here".
>>>
>>> Person handling the patches IS the maintainer. Full stop.
>>
>> Based on email you forwarded to me and some more feedback I got, I think
>> I understood what would be the solution to satisfy your point of not
>> changing existing entry and solve my problem of maintainer handling
>> patches not being listed anywhere as maintainer. I will solve it v2.
>>
>> Best regards,
>> Krzysztof
> 
> Doh, this is definitely my bad, I should have made a _new_ entry in 
> MAINTAIENRS similar to this.
> 
> AIROHA PCIE PHY DRIVER
> M:      Lorenzo Bianconi <lorenzo@...nel.org>
> L:      linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
> S:      Maintained
> F:      Documentation/devicetree/bindings/phy/airoha,en7581-pcie-phy.yaml
> F:      drivers/phy/phy-airoha-pcie-regs.h
> F:      drivers/phy/phy-airoha-pcie.c
> 
> GENERIC PHY FRAMEWORK
> M:      Vinod Koul <vkoul@...nel.org>
> M:      Kishon Vijay Abraham I <kishon@...nel.org>
> L:      linux-phy@...ts.infradead.org
> S:      Supported
> Q:      https://patchwork.kernel.org/project/linux-phy/list/
> T:      git git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git
> F:      Documentation/devicetree/bindings/phy/
> F:      drivers/phy/
> F:      include/dt-bindings/phy/
> F:      include/linux/phy/
> 
> scripts/get_maintainer.pl drivers/phy/phy-airoha-pcie.c
> Lorenzo Bianconi <lorenzo@...nel.org> (maintainer:AIROHA PCIE PHY DRIVER)
> Vinod Koul <vkoul@...nel.org> (maintainer:GENERIC PHY FRAMEWORK)
> Kishon Vijay Abraham I <kishon@...nel.org> (maintainer:GENERIC PHY 
> FRAMEWORK)
> linux-arm-kernel@...ts.infradead.org (moderated list:AIROHA PCIE PHY DRIVER)
> linux-phy@...ts.infradead.org (open list:GENERIC PHY FRAMEWORK)
> linux-kernel@...r.kernel.org (open list)
> GENERIC PHY FRAMEWORK status: Supported
> 
> Its 1:1 what we have for drivers/media/platform/qcom
> 
> I'll add that entry and leave the Iris/Venus entries as-is.

Any progress on this? We agreed you will be sending that, but I think it
did not happen, so maybe you want me to send it?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ