From: Matthias Kaehlcke <mka@google.com>
To: Owen Yang <ecs.taipeikernel@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Abner Yen <abner.yen@ecs.corp-partner.google.com>,
Gavin Lee <gavin.lee@ecs.corp-partner.google.com>,
Harvey <hunge@google.com>, Stephen Boyd <swboyd@chromium.org>,
Bob Moragues <moragues@google.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: arm: qcom: Add zombie
Date: Mon, 28 Nov 2022 17:16:20 +0000 [thread overview]
Message-ID: <Y4Ts5KPJMb6Rh8DP@google.com> (raw)
In-Reply-To: <20221125174415.v5.1.Idfcba5344b7995b44b7fa2e20f1aa4351defeca6@changeid>
On Fri, Nov 25, 2022 at 05:44:24PM +0800, Owen Yang wrote:
> Add an entry in the device tree binding for sc7280-zombie.
>
> Signed-off-by: Owen Yang <ecs.taipeikernel@gmail.com>
> ---
>
> (no changes since v1)
That is not correct. As far as I recall there were at least changes in the
position at which the new entries are inserted and some changes in the commit
message too.
It's not super important for a trivial patch like this, but please make it
a habit to post an accurate change log for each version.
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
prev parent reply other threads:[~2022-11-28 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 9:44 [PATCH v5 1/2] dt-bindings: arm: qcom: Add zombie Owen Yang
2022-11-25 9:44 ` [PATCH v5 2/2] arm64: dts: qcom: sc7280: Add DT for sc7280-herobrine-zombie Owen Yang
2022-11-28 16:55 ` Matthias Kaehlcke
2022-11-28 16:58 ` Doug Anderson
2022-11-25 10:13 ` [PATCH v5 1/2] dt-bindings: arm: qcom: Add zombie Krzysztof Kozlowski
2022-11-28 16:58 ` Doug Anderson
2022-11-28 17:16 ` Matthias Kaehlcke [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=Y4Ts5KPJMb6Rh8DP@google.com \
--to=mka@google.com \
--cc=abner.yen@ecs.corp-partner.google.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ecs.taipeikernel@gmail.com \
--cc=gavin.lee@ecs.corp-partner.google.com \
--cc=hunge@google.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=moragues@google.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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.