From: Bryan O'Donoghue <bod@kernel.org>
To: Denny Lin <dennylin0707@gmail.com>
Cc: Vikash Garodia <vikash.garodia@oss.qualcomm.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
Subject: Re: [PATCH v3] media: qcom: iris: guard IRQ handler with runtime PM check
Date: Thu, 4 Jun 2026 12:12:42 +0100 [thread overview]
Message-ID: <acdd8e10-ed52-4dcc-9c1c-3665f7193a20@kernel.org> (raw)
In-Reply-To: <CAGEkeHeFJC_eMZnDbbjXZs+Gy424YdCNH-HswPgE3zyYrEnoDA@mail.gmail.com>
On 04/06/2026 10:07, Denny Lin wrote:
>> Could you please put your series of individual patches but group them
>> into a consistent list - so that I/we don't have to figure our how to
>> apply them and in which order.
> Sure. If patches are related or have an intended application order,
> I'll group them into a patch series in future submissions to make that
> clearer.
>
> Thanks,
> Hungyu
Its just a bit confusing what you are doing here v1, v2, v3 in quick
succession over a few topics in the same driver.
This feels like an aggregate fixes series. If the patches are
individually applicable - great that's exactly what we want but,
separating a series of fixes into individual bits and sending them out
in quick succession is a bit of a mess in patchwork.
So could you _please_ just aggregate your fixes into a series so that
the ordering is implicit - if ordering matters and the history of the
reworking is contained in the series overview.
ty
---
bod
next prev parent reply other threads:[~2026-06-04 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v2-message-id>
2026-06-04 8:25 ` Hungyu Lin
2026-06-04 8:44 ` Bryan O'Donoghue
2026-06-04 9:07 ` Denny Lin
2026-06-04 11:12 ` Bryan O'Donoghue [this message]
2026-06-04 12:06 ` Denny Lin
2026-06-04 12:08 ` Bryan O'Donoghue
2026-06-04 13:25 ` Dmitry Baryshkov
2026-06-04 14:55 ` Denny Lin
2026-06-07 20:42 ` Dmitry Baryshkov
2026-06-07 20:40 ` Dmitry Baryshkov
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=acdd8e10-ed52-4dcc-9c1c-3665f7193a20@kernel.org \
--to=bod@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=dennylin0707@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
Powered by JetHome