From: Dzmitry Sankouski <dsankouski@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: add samsung,starqltechn board based on sdm845 chip
Date: Mon, 17 Oct 2022 11:02:38 +0300 [thread overview]
Message-ID: <CABTCjFAajiT7QpyA9mG7i4XzWxtLsvRsDLPtWTvwmJbMYEr1SQ@mail.gmail.com> (raw)
In-Reply-To: <8c773f11-1c00-1856-daa7-250a4ec37d23@linaro.org>
пт, 14 окт. 2022 г. в 19:13, Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org>:
>
> On 14/10/2022 07:01, Dzmitry Sankouski wrote:
> > чт, 13 окт. 2022 г. в 16:43, Krzysztof Kozlowski
> > <krzysztof.kozlowski@linaro.org>:
> >>
> >> On 12/10/2022 14:54, Dzmitry Sankouski wrote:
> >>> Add samsung,starqltechn board (Samsung Galaxy S9) binding.
> >>>
> >>> Signed-off-by: Dzmitry Sankouski <dsankouski@gmail.com>
> >>> ---
> >>> Changes for v2,v3: none
> >>
> >> Where is v2 and v3 of this?
> > I've been told it's easier for maintainers to resend all patch series,
> > even if only 1 patch from the series requires change. So I decided to
> > keep versions equal in all patches, to clearly indicate those patches
> > are from the same series. Please, correct me if I'm wrong.
>
> This is okay, but you wrote here there was a v1 and v2, and you changed
> nothing against it. If there was v1 and v2, we would ack it, I think.
>
> Or this changelog is for some other patch? Not for this one?
There's no previous versions of this patch, since it was born in the
v3 patch series. The empty changelog for this patch indicates that
there's no point to look for previous versions. I think I'll do it
differently next time to avoid confusion - just a sentence that vN is
the start version for patch.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-10-17 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:54 [PATCH v3 0/2] add device Samsung Galaxy S9 phone (codename starqltechn) and board binding Dzmitry Sankouski
2022-10-12 18:54 ` [PATCH v3 1/2] dt-bindings: arm: add samsung,starqltechn board based on sdm845 chip Dzmitry Sankouski
2022-10-13 13:43 ` Krzysztof Kozlowski
2022-10-14 11:01 ` Dzmitry Sankouski
2022-10-14 16:10 ` Krzysztof Kozlowski
2022-10-17 8:02 ` Dzmitry Sankouski [this message]
2022-10-18 2:04 ` Krzysztof Kozlowski
2022-10-12 18:54 ` [PATCH v3 2/2] arm64: dts: qcom: starqltechn: add initial device tree for starqltechn Dzmitry Sankouski
2022-11-07 3:12 ` [PATCH v3 0/2] add device Samsung Galaxy S9 phone (codename starqltechn) and board binding Bjorn Andersson
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=CABTCjFAajiT7QpyA9mG7i4XzWxtLsvRsDLPtWTvwmJbMYEr1SQ@mail.gmail.com \
--to=dsankouski@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).