From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Bryan O'Donoghue <bod@kernel.org>
Cc: Abhinav Kumar <abhinav.kumar@linux.dev>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vishnu Reddy <busanna.reddy@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH v4 6/6] media: iris: Introduce vpu ops for vpu4 with necessary hooks
Date: Fri, 16 Jan 2026 12:53:25 +0100 [thread overview]
Message-ID: <cc6e1fdd-f15f-4d31-b2c6-1fb59938786c@kernel.org> (raw)
In-Reply-To: <b6a89ccc-45da-a4eb-df69-29e80dbe3655@oss.qualcomm.com>
On 16/01/2026 12:30, Dikshita Agarwal wrote:
>>
>> I think this review timeline is final argument for Vikash to stop
>> pushing such narratives and complains, because your review is expected
>> to be BEFORE the maintainer upper in the upstream flow.
>
> Since these changes were posted by Vikash, who is a co‑maintainer of this
> driver, I initially waited for reviews from other community members before
> adding my own tags. We did receive review comments on most of the patches,
This is not how it works.
> and I intentionally held back my Reviewed-by tags to allow space for
> broader feedback.
>
> Now that the series has been on the mailing list for about a month without
> any remaining open comments, I have gone ahead and reviewed the patches,
You as a driver maintainer should review within few days, week maximum.
Not a month. And IT IS DOCUMENTED.
You do not need to wait for anyone in the community for performing your
side of driver review. Performing review after one month is not really
responsible, but the only party you affect is your own team, so sure, I
don't mind.
But DO NOT apply such rule of waiting months for the rest of the community.
Please read Documentation/maintainer/feature-and-driver-maintainers.rst
which gives you clear guidelines what is expected, including the
timeline. If you disagree and claim Iris is maintained by you in
weeks-time (one month), that rule will apply to all of us, entire
community and also to Bryan - we all can look at patches to Iris within
that timeframe.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-01-16 11:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 12:35 [PATCH v4 0/6] media: iris: prepare support for video codecs on Qcom vpu4 platform Vikash Garodia
2025-12-10 12:35 ` [PATCH v4 1/6] media: iris: Add support for multiple clock sources Vikash Garodia
2026-01-16 9:38 ` Dikshita Agarwal
2025-12-10 12:36 ` [PATCH v4 2/6] media: iris: Add support for multiple TZ content protection(CP) configs Vikash Garodia
2026-01-16 9:39 ` Dikshita Agarwal
2025-12-10 12:36 ` [PATCH v4 3/6] media: iris: Introduce buffer size calculations for vpu4 Vikash Garodia
2026-01-16 10:31 ` Dikshita Agarwal
2025-12-10 12:36 ` [PATCH v4 4/6] media: iris: Move vpu register defines to common header file Vikash Garodia
2025-12-10 15:03 ` Dmitry Baryshkov
2025-12-10 15:47 ` Vikash Garodia
2025-12-10 21:26 ` Bryan O'Donoghue
2025-12-10 23:35 ` Dmitry Baryshkov
2026-01-16 9:45 ` Dikshita Agarwal
2025-12-10 12:36 ` [PATCH v4 5/6] media: iris: Move vpu35 specific api to common to use for vpu4 Vikash Garodia
2026-01-16 9:47 ` Dikshita Agarwal
2025-12-10 12:36 ` [PATCH v4 6/6] media: iris: Introduce vpu ops for vpu4 with necessary hooks Vikash Garodia
2026-01-16 9:51 ` Dikshita Agarwal
2026-01-16 10:46 ` Krzysztof Kozlowski
2026-01-16 11:27 ` Vikash Garodia
2026-01-16 11:54 ` Krzysztof Kozlowski
2026-01-16 12:58 ` Bryan O'Donoghue
2026-01-16 11:30 ` Dikshita Agarwal
2026-01-16 11:53 ` Krzysztof Kozlowski [this message]
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=cc6e1fdd-f15f-4d31-b2c6-1fb59938786c@kernel.org \
--to=krzk@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=busanna.reddy@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.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=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=vikash.garodia@oss.qualcomm.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®