From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Alexandru M Stan <amstan@chromium.org>
Subject: [PATCH v2 0/2] Update fingerprint node on herobrine/trogdor
Date: Mon, 7 Nov 2022 11:15:33 -0800 [thread overview]
Message-ID: <20221107191535.624371-1-swboyd@chromium.org> (raw)
This patch series updates the binding for the Trogdor and Herobrine
boards' fingerprint node. Now that the binding has been accepted[1]
we're ready to merge this in the qcom tree.
Changes from v1 (https://lore.kernel.org/r/20220317010640.2498502-1-swboyd@chromium.org):
* New patch for trogdor
Stephen Boyd (2):
arm64: dts: qcom: Fully describe fingerprint node on Herobrine
arm64: dts: qcom: Fully describe fingerprint node on Trogdor
arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 20 +++++++++++++++++--
.../arm64/boot/dts/qcom/sc7280-herobrine.dtsi | 5 ++++-
2 files changed, 22 insertions(+), 3 deletions(-)
Cc: Douglas Anderson <dianders@chromium.org>
Cc: Matthias Kaehlcke <mka@chromium.org>
Cc: Alexandru M Stan <amstan@chromium.org>
[1] https://lore.kernel.org/r/166718941539.790.4332712127794687523.git-patchwork-notify@kernel.org
base-commit: 95fade4016cbd57ee050ab226c8f0483af1753c4
--
https://chromeos.dev
next reply other threads:[~2022-11-07 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:15 Stephen Boyd [this message]
2022-11-07 19:15 ` [PATCH v2 1/2] arm64: dts: qcom: Fully describe fingerprint node on Herobrine Stephen Boyd
2022-11-08 1:22 ` Doug Anderson
2022-11-07 19:15 ` [PATCH v2 2/2] arm64: dts: qcom: Fully describe fingerprint node on Trogdor Stephen Boyd
2022-11-08 1:22 ` Doug Anderson
2022-11-09 0:56 ` Stephen Boyd
2022-11-08 4:36 ` (subset) [PATCH v2 0/2] Update fingerprint node on herobrine/trogdor Bjorn Andersson
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=20221107191535.624371-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=amstan@chromium.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®