From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: mka@chromium.org, dianders@chromium.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.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 1/2] arm64: dts: qcom: sc7280: Add device tree for herobrine evoker
Date: Thu, 1 Sep 2022 10:59:06 +0300 [thread overview]
Message-ID: <6295abda-e1d3-42fc-36af-8c59deaaf5e1@linaro.org> (raw)
In-Reply-To: <20220901141304.1.I7dd7a79c4cc5fe91c3feb004473feb3b34b7b2d8@changeid>
On 01/09/2022 09:13, Sheng-Liang Pan wrote:
> Add a basic device tree for the herobrine evoker board.
>
> Signed-off-by: Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com>
I am pretty sure I saw it... Where is the changelog and versioning?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-01 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 6:13 [PATCH 0/2] Add a new board device tree named 'evoker' for herobrine variant Sheng-Liang Pan
2022-09-01 6:13 ` [PATCH 1/2] arm64: dts: qcom: sc7280: Add device tree for herobrine evoker Sheng-Liang Pan
2022-09-01 7:59 ` Krzysztof Kozlowski [this message]
2022-09-01 6:13 ` [PATCH 2/2] dt-bindings: arm: qcom: document sc7280 and evoker board Sheng-Liang Pan
2022-09-01 7:58 ` Krzysztof Kozlowski
2022-09-01 9:12 [PATCH 0/2] Add a new board device tree named 'evoker' for herobrine variant Sheng-Liang Pan
2022-09-01 9:12 ` [PATCH 1/2] arm64: dts: qcom: sc7280: Add device tree for herobrine evoker Sheng-Liang Pan
2022-09-01 10:01 ` Krzysztof Kozlowski
2022-09-01 15:06 ` Doug Anderson
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=6295abda-e1d3-42fc-36af-8c59deaaf5e1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.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=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=sheng-liang.pan@quanta.corp-partner.google.com \
/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.