mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
	bryan.odonoghue@linaro.org,
	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 08:44:42 +0200	[thread overview]
Message-ID: <b83cc20b-44d2-4635-a540-7a9c0d36cdb5@linaro.org> (raw)
In-Reply-To: <8772c48f-348b-8a68-2099-562a29b9dd8d@quicinc.com>

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?

Sorry, this is already happening.

Your push back here is odd, impolite and really disappointing. You
actually should be happy that person outside wants to care about this
driver...

> Hi Hans,
> 
> Incase you would like to split sending PRs, as the contributions for Venus/Iris
> would be significantly higher, let us know, we can pick that up separately.

Considering quality of the code you sent as Iris upstreaming, you are
not there yet.

https://lore.kernel.org/all/1690550624-14642-1-git-send-email-quic_vgarodia@quicinc.com/

Please learn, read how the process works, what is the responsibility of
maintainers first.


Best regards,
Krzysztof

  reply	other threads:[~2025-07-15  6:44 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 [this message]
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
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=b83cc20b-44d2-4635-a540-7a9c0d36cdb5@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=abhinav.kumar@linux.dev \
    --cc=bryan.odonoghue@linaro.org \
    --cc=hverkuil@xs4all.nl \
    --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®