From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: konrad.dybcio@somainline.org, Dzmitry Sankouski <dsankouski@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v9 0/2] add device Xiaomi Mi 6 (codename sagit) and board binding
Date: Thu, 13 Oct 2022 09:41:40 -0400 [thread overview]
Message-ID: <e1e8b136-4be4-bebb-71af-fa3eed02272f@linaro.org> (raw)
In-Reply-To: <82891b0026f8f43b266245c7c0c85a98@somainline.org>
On 12/10/2022 15:25, konrad.dybcio@somainline.org wrote:
> On 2022-10-12 20:52, Dzmitry Sankouski wrote:
>> Add initial support for Xiaomi Mi 6 phone (codename sagit)
>>
>> Dzmitry Sankouski (2):
>> dt-bindings: arm: add xiaomi,sagit board based on msm8998 chip
>> arm64: dts: qcom: sagit: add initial device tree for sagit
>>
> Looks like you resent this series just to add the A-b on the dt-bindings
> patch?
> If that's the case, you don't have to do it, the maintainer will pick up
> the tags
> when applying your patch and an essentially empty revision just adds
> confusion.
The ack was ignored in last two previous revisions, so the resend was
needed. Maintainer would not find that ack...
Best regards,
Krzysztof
prev parent reply other threads:[~2022-10-13 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:52 [PATCH v9 0/2] add device Xiaomi Mi 6 (codename sagit) and board binding Dzmitry Sankouski
2022-10-12 18:52 ` [PATCH v9 1/2] dt-bindings: arm: add xiaomi,sagit board based on msm8998 chip Dzmitry Sankouski
2022-10-12 18:52 ` [PATCH v9 2/2] arm64: dts: qcom: sagit: add initial device tree for sagit Dzmitry Sankouski
2022-10-12 19:28 ` konrad.dybcio
2022-10-12 19:25 ` [PATCH v9 0/2] add device Xiaomi Mi 6 (codename sagit) and board binding konrad.dybcio
2022-10-13 13:41 ` 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=e1e8b136-4be4-bebb-71af-fa3eed02272f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsankouski@gmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@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).