From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
linux-media@vger.kernel.org, stanimir.k.varbanov@gmail.com,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, mchehab@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/4] venus: add support for 10 bit decoding
Date: Thu, 4 May 2023 15:28:10 +0100 [thread overview]
Message-ID: <b79dcf81-2eb4-c376-e1a8-e947ffa6c70a@nexus-software.ie> (raw)
In-Reply-To: <facc9800-6af4-5cb3-bd22-b22b2250090a@quicinc.com>
On 04/05/2023 15:04, Vikash Garodia wrote:
>> Doh I see you did most of that - just missed the V2.
>>
>> Please remember to version your subsequent series. "git format-patch -v2"
>
> Does this qualify for a version upgrade when a single patch is
> subsequently raised as series ? IMO, the link
>
> to previous single patch in cover letter and then starting the series
> (as v0) seems to provide the required info.
Hmm. I'd say any series should have an increment in it to differentiate,
with the exception being RESEND.
Also you are splitting one patch into four.
Looking through a bunch of email it might be not immediately obvious to
understand that the new series and old series differ, which is IMO how
the version numbers help others to know what's going on.
---
bod
prev parent reply other threads:[~2023-05-04 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 10:36 [PATCH 0/4] venus: add support for 10 bit decoding Dikshita Agarwal
2023-05-04 10:36 ` [PATCH 1/4] venus: add support for V4L2_PIX_FMT_P010 color format Dikshita Agarwal
2023-05-04 17:18 ` Konrad Dybcio
2023-05-04 10:36 ` [PATCH 2/4] venus: update calculation for dpb buffers Dikshita Agarwal
2023-05-04 17:29 ` Konrad Dybcio
2023-05-04 17:30 ` Konrad Dybcio
2023-05-04 10:36 ` [PATCH 3/4] venus: add handling of bit depth change from firmwar Dikshita Agarwal
2023-05-04 17:32 ` Konrad Dybcio
2023-05-04 10:36 ` [PATCH 4/4] venus: return P010 as preferred format for 10 bit decode Dikshita Agarwal
2023-05-04 17:20 ` Konrad Dybcio
2023-05-05 9:03 ` Dikshita Agarwal
2023-05-05 10:42 ` Konrad Dybcio
2023-05-05 11:03 ` Dmitry Baryshkov
2023-05-04 13:49 ` [PATCH 0/4] venus: add support for 10 bit decoding Bryan O'Donoghue
2023-05-04 13:51 ` Bryan O'Donoghue
2023-05-04 14:04 ` Vikash Garodia
2023-05-04 14:28 ` Bryan O'Donoghue [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=b79dcf81-2eb4-c376-e1a8-e947ffa6c70a@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=konrad.dybcio@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 \
--cc=stanimir.k.varbanov@gmail.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