From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Doug Anderson <dianders@chromium.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sc7280: Add "google,senor" to the compatible
Date: Thu, 29 Apr 2021 09:43:23 -0400 (EDT) [thread overview]
Message-ID: <a26e7152-208e-3343-a9f8-8dfdeb222aeb@crashcourse.ca> (raw)
In-Reply-To: <CAD=FV=UUowpvn_2uPrOQG9hOCdX6GYZDojBdW+w8hg5q6PfvAQ@mail.gmail.com>
On Thu, 29 Apr 2021, Doug Anderson wrote:
> Hi,
>
> On Wed, Apr 28, 2021 at 10:40 PM Rajendra Nayak <rnayak@codeaurora.org> wrote:
> >
> > The sc7280 IDP board is also called senor in the Chrome OS builds.
> > Add the "google,senor" compatible so coreboot/depthcharge knows what
> > device tree blob to pick
> >
> > Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> > ---
> > arch/arm64/boot/dts/qcom/sc7280-idp.dts | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
subject line contains "google,senor"
rday
next prev parent reply other threads:[~2021-04-29 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 5:40 [PATCH 1/2] dt-bindings: arm: qcom: Document google,senor board Rajendra Nayak
2021-04-29 5:40 ` [PATCH 2/2] arm64: dts: qcom: sc7280: Add "google,senor" to the compatible Rajendra Nayak
2021-04-29 12:46 ` Matthias Kaehlcke
2021-04-29 13:39 ` Doug Anderson
2021-04-29 13:43 ` Robert P. J. Day [this message]
2021-04-30 4:19 ` Rajendra Nayak
2021-04-29 12:43 ` [PATCH 1/2] dt-bindings: arm: qcom: Document google,senor board Matthias Kaehlcke
2021-04-29 13:39 ` Doug Anderson
2021-05-03 19:32 ` Rob Herring
2021-06-01 0:10 ` patchwork-bot+linux-arm-msm
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=a26e7152-208e-3343-a9f8-8dfdeb222aeb@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--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.