[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <09ccfa54-5ada-8dff-03a2-b2ffb07a58c1@linaro.org>
Date: Mon, 12 Jun 2023 03:25:42 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Jagadeesh Kona <quic_jkona@...cinc.com>,
Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Taniya Das <quic_tdas@...cinc.com>,
Satya Priya Kakitapalli <quic_skakitap@...cinc.com>,
Imran Shaik <quic_imrashai@...cinc.com>,
Ajit Pandey <quic_ajipan@...cinc.com>
Subject: Re: [PATCH V4 0/4] Add camera clock controller support for SM8550
On 09/06/2023 12:50, Jagadeesh Kona wrote:
> Add bindings, driver and devicetree node for camera clock controller on
> SM8550.
This is very confusing.
Your cover letter doesn't detail any changes and your individual patches
all say "no changes since v3", "no changes since v2"
If this is a RESEND then mark it as a RESEND.
Good practice is to for example add a note that says
"I looked at updating the yaml for the camcc but opted to do this in
another series" or "opted not to do this at this time" or "it doesn't
make sense because of X"
https://lore.kernel.org/linux-arm-msm/546876ba-970d-5cd5-648e-723698ca74fd@linaro.org/
Could you perhaps RESEND this V4 with a log that explains what has
changed from one version to the next.
If nothing has changed then don't bump the version prefix with RESEND..
Second thought even replying to your cover email with the changelog
would do.....
---
bod
Powered by blists - more mailing lists