From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH] media: iris: MAINTAINERS: Document actual maintainership by Bryan O'Donoghue
Date: Tue, 15 Jul 2025 12:03:01 +0100 [thread overview]
Message-ID: <2b5ececb-fbf7-4901-8efb-03744f740836@linaro.org> (raw)
In-Reply-To: <c70fd6c6-1a65-41ee-b0e1-f6c792867009@linaro.org>
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@kernel.org>
L: linux-arm-kernel@lists.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@kernel.org>
M: Kishon Vijay Abraham I <kishon@kernel.org>
L: linux-phy@lists.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@kernel.org> (maintainer:AIROHA PCIE PHY DRIVER)
Vinod Koul <vkoul@kernel.org> (maintainer:GENERIC PHY FRAMEWORK)
Kishon Vijay Abraham I <kishon@kernel.org> (maintainer:GENERIC PHY
FRAMEWORK)
linux-arm-kernel@lists.infradead.org (moderated list:AIROHA PCIE PHY DRIVER)
linux-phy@lists.infradead.org (open list:GENERIC PHY FRAMEWORK)
linux-kernel@vger.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
next prev parent reply other threads:[~2025-07-15 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 15:16 Krzysztof Kozlowski
2025-07-15 5:51 ` Vikash Garodia
2025-07-15 6:44 ` Krzysztof Kozlowski
2025-07-15 7:00 ` Vikash Garodia
2025-07-15 7:06 ` Krzysztof Kozlowski
2025-07-15 9:20 ` Krzysztof Kozlowski
2025-07-15 11:03 ` Bryan O'Donoghue [this message]
2025-08-12 8:26 ` Krzysztof Kozlowski
2025-08-12 8:31 ` Bryan O'Donoghue
2025-07-15 7:18 ` Krzysztof Kozlowski
2025-07-15 9:04 ` Bryan O'Donoghue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b5ececb-fbf7-4901-8efb-03744f740836@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=abhinav.kumar@linux.dev \
--cc=hverkuil@xs4all.nl \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®