From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
Douglas Anderson <dianders@chromium.org>
Cc: linux-kernel@vger.kernel.org,
"Joseph S . Barrera III" <joebar@chromium.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Alexandru M Stan <amstan@chromium.org>,
devicetree@vger.kernel.org, Julius Werner <jwerner@chromium.org>,
linux-doc@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
patches@lists.linux.dev, Matthias Kaehlcke <mka@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH v4 1/5] dt-bindings: Document how Chromebooks with depthcharge boot
Date: Mon, 27 Jun 2022 15:02:40 -0500 [thread overview]
Message-ID: <165636016348.3080661.58233739131121561.b4-ty@linaro.org> (raw)
In-Reply-To: <20220520143502.v4.1.I71e42c6174f1cec17da3024c9f73ba373263b9b6@changeid>
On Fri, 20 May 2022 14:38:41 -0700, Douglas Anderson wrote:
> This documents how many Chromebooks pick the device tree that will be
> passed to the OS and can help understand the revisions / SKUs listed
> as the top-level "compatible" in many Chromebooks.
>
>
Applied, thanks!
[1/5] dt-bindings: Document how Chromebooks with depthcharge boot
commit: 59228d3b9060b0e5e6b37ceca078fd81a165cfc9
[2/5] dt-bindings: arm: qcom: Mention that Chromebooks use a different scheme
commit: dbbccb3db122558b35ecb4c87a86bbad37c80862
[3/5] dt-bindings: arm: qcom: Add sc7180 Chromebook board bindings
commit: 3b8bfe002c4ba633b48cc497238a69eb88346a60
[4/5] dt-bindings: arm: qcom: Add / fix sc7280 board bindings
commit: 707b9b08789bf3312c9cf23c621ad942de9aa48c
[5/5] dt-bindings: arm: qcom: Add more sc7180 Chromebook board bindings
commit: 5069fe941f76c9f37abc98636a7db33a5ac72840
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
prev parent reply other threads:[~2022-06-27 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 21:38 [PATCH v4 1/5] dt-bindings: Document how Chromebooks with depthcharge boot Douglas Anderson
2022-05-20 21:38 ` [PATCH v4 2/5] dt-bindings: arm: qcom: Mention that Chromebooks use a different scheme Douglas Anderson
2022-05-22 7:54 ` Krzysztof Kozlowski
2022-05-20 21:38 ` [PATCH v4 3/5] dt-bindings: arm: qcom: Add sc7180 Chromebook board bindings Douglas Anderson
2022-05-22 7:57 ` Krzysztof Kozlowski
2022-05-23 16:16 ` Doug Anderson
2022-05-24 9:34 ` Krzysztof Kozlowski
2022-05-24 23:00 ` Doug Anderson
2022-05-20 21:38 ` [PATCH v4 4/5] dt-bindings: arm: qcom: Add / fix sc7280 " Douglas Anderson
2022-06-22 8:27 ` Krzysztof Kozlowski
2022-06-22 13:51 ` Doug Anderson
2022-05-20 21:38 ` [PATCH v4 5/5] dt-bindings: arm: qcom: Add more sc7180 Chromebook " Douglas Anderson
2022-05-22 8:01 ` Krzysztof Kozlowski
2022-05-23 16:19 ` Doug Anderson
2022-06-01 23:26 ` Rob Herring
2022-06-27 20:02 ` Bjorn Andersson [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=165636016348.3080661.58233739131121561.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=amstan@chromium.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=joebar@chromium.org \
--cc=jwerner@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
--cc=quic_rjendra@quicinc.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.