From: Johan Hovold <johan@kernel.org>
To: Parikshit Pareek <quic_ppareek@quicinc.com>
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 3/3] arm64: dts: qcom: introduce sa8540p-ride dts
Date: Tue, 26 Jul 2022 15:54:13 +0200 [thread overview]
Message-ID: <Yt/yBbIvav1+TE5s@hovoldconsulting.com> (raw)
In-Reply-To: <20220722143711.17563-1-quic_ppareek@quicinc.com>
On Fri, Jul 22, 2022 at 08:07:11PM +0530, Parikshit Pareek wrote:
> Create new dts file specific for Qdrive board based on sa8540p chipset.
> Introduce common dtsi file sa8295p-adp.dtsi, to be included for adp and
> Qdrive board.
>
> Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
> ---
>
> Changes since v1:
> - Add , after year 2022, in the license header
> - Rename the dtsi which is suitable for common to many ADP boards
> - Correct the allignment in the Makefile
> - Split the patch in introducing common dtsi file, and adding new board
> file
This changelog would probably make more sense in a cover letter. Also
your patches are not threaded (e.g. don't show up as a series in out
mail clients or on lore).
Please consider using git-format-patch (which has a --cover-letter
switch) for generating the series and git-send-email for sending, which
should help with both issues.
Johan
prev parent reply other threads:[~2022-07-26 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 14:37 [PATCH v2 3/3] arm64: dts: qcom: introduce sa8540p-ride dts Parikshit Pareek
2022-07-26 13:54 ` Johan Hovold [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=Yt/yBbIvav1+TE5s@hovoldconsulting.com \
--to=johan@kernel.org \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_ppareek@quicinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.