From: Matthias Kaehlcke <mka@chromium.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
quic_rjendra@quicinc.com, sibis@codeaurora.org,
kgodara1@codeaurora.org, swboyd@chromium.org,
pmaliset@codeaurora.org, Andy Gross <agross@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: qcom: sc7280: Move herobrine-r0 to its own dts
Date: Fri, 14 Jan 2022 06:15:43 -0800 [thread overview]
Message-ID: <YeGFj/lfCLn79yzw@google.com> (raw)
In-Reply-To: <20220113164233.2.Id9716db8c133bcb14c9413144048f8d00ae2674f@changeid>
On Thu, Jan 13, 2022 at 04:43:01PM -0800, Douglas Anderson wrote:
> The upcoming herobrine-r1 board is really not very similar to
> herobrine-r0. Let's get rid of the "herobrine.dtsi" file and stick all
> the content in the -r0 dts file directly. We'll also rename the dts so
> it's obvious that it's just for -r0.
>
> While renaming, let's actually name the file so it's obvious that
> "herobrine" is both the name of the board and the name of the
> "baseboard". In other words "herobrine" is an actual board but also
> often used as the name of a whole class of similar boards that forked
> from a design. While "herobrine-herobrine" is a bit of mouthful it
> makes it more obvious which things are part of an actual board rather
> than the baseboard.
>
> NOTE: herobrine-rev0's days are likely doomed and this device tree is
> likely to be deleted in the future.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2022-01-14 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 0:42 [PATCH 0/4] arm64: dts: qcom: sc7280: Introduce herobrine-rev1 Douglas Anderson
2022-01-14 0:43 ` [PATCH 1/4] arm64: dts: qcom: sc7280: Fix gmu unit address Douglas Anderson
2022-01-14 6:08 ` Stephen Boyd
2022-01-14 15:02 ` Doug Anderson
2022-01-14 17:33 ` Matthias Kaehlcke
2022-01-14 0:43 ` [PATCH 2/4] arm64: dts: qcom: sc7280: Move herobrine-r0 to its own dts Douglas Anderson
2022-01-14 6:09 ` Stephen Boyd
2022-01-14 14:15 ` Matthias Kaehlcke [this message]
2022-01-14 0:43 ` [PATCH 3/4] arm64: dts: qcom: sc7280: Factor out Chrome common fragment Douglas Anderson
2022-01-14 6:15 ` Stephen Boyd
2022-01-14 14:24 ` Matthias Kaehlcke
2022-01-14 0:43 ` [PATCH 4/4] arm64: dts: qcom: sc7280: Add herobrine-r1 Douglas Anderson
2022-01-14 6:25 ` Stephen Boyd
2022-01-14 17:11 ` Matthias Kaehlcke
2022-01-21 18:00 ` Konrad Dybcio
2022-01-21 21:44 ` 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=YeGFj/lfCLn79yzw@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kgodara1@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmaliset@codeaurora.org \
--cc=quic_rjendra@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.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.