Message-ID: <2b5ececb-fbf7-4901-8efb-03744f740836@linaro.org>
Date: Tue, 15 Jul 2025 12:03:01 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...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 10:20, Krzysztof Kozlowski wrote:
> On 15/07/2025 09:06, Krzysztof Kozlowski wrote:
>> On 15/07/2025 09:00, Vikash Garodia wrote:
>>>
>>> On 7/15/2025 12:14 PM, Krzysztof Kozlowski wrote:
>>>> On 15/07/2025 07:51, Vikash Garodia wrote:
>>>>>
>>>>> On 7/14/2025 8:46 PM, Krzysztof Kozlowski wrote:
>>>>>> Bryan O'Donoghue reviews and applies patches for both Iris and Venus
>>>>>> Qualcomm SoC video codecs (visible in git log as his Signed-off-by and
>>>>>> in pull requests like [1]), so he is de facto the maintainer responsible
>>>>>> for the code.  Reflect this actual state my changing his entry from
>>>>>> reviewer to maintainer and moving the entry to alphabetical position by
>>>>>> first name.
>>>>>
>>>>> NAK.
>>>>>
>>>>> The roles and responsibilities are well agreed by media maintainer(Hans), with
>>>>> Bryan part of that discussion, w.r.t code contributions to iris and sending
>>>>> patches to media tree. The only reason Bryan post the patches is that Hans wants
>>>>> single PR for patches across Qualcomm media drivers (Camss/Videoss)
>>>>
>>>> That's the maintainer role, so Bryan is the maintainer. I am documenting
>>>> actual status and your NAK is naking what? That Bryan cannot handle patches?
>>> I would say, you are reading too much into it, i updated what we have discussed
>>> and agreed upon the different roles for managing venus and iris drivers.
>>
>> 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.

---
bod

Powered by blists - more mailing lists