From: Parikshit Pareek <quic_ppareek@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: qcom: Document additional sa8540p device
Date: Mon, 25 Jul 2022 15:07:29 +0530 [thread overview]
Message-ID: <20220725093729.GA19730@hu-ppareek-blr.qualcomm.com> (raw)
In-Reply-To: <de7fc091-ed12-c585-d39d-2bcf2bda37fe@linaro.org>
On Fri, Jul 22, 2022 at 08:27:39PM +0200, Krzysztof Kozlowski wrote:
> On 22/07/2022 16:25, Parikshit Pareek wrote:
> > Add the ADP ride device to the valid device compatibles found on the
> > sa8540p platform.
> >
> > Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
>
> Please add Acked-by/Reviewed-by tags when posting new versions. However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
>
> https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540
>
> If a tag was not added on purpose, please state why and what changed.
My mistake, I missed the tags.
>
>
> Additionally - please thread your patchset. Git send-email does it by
> default. If you use other tools - be sure the effect is threaded.
Used git send-email. May be happened due to the change in one of the commit headers in one of the patches.
> Otherwise it is not possible to find the patches from you.
>
>
> Best regards,
> Krzysztof
Regards,
Parikshit Pareek
prev parent reply other threads:[~2022-07-25 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 14:25 Parikshit Pareek
2022-07-22 18:27 ` Krzysztof Kozlowski
2022-07-25 9:37 ` Parikshit Pareek [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=20220725093729.GA19730@hu-ppareek-blr.qualcomm.com \
--to=quic_ppareek@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.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
all inboxes | Powered by JetHome®