From: patchwork-bot+linux-arm-msm@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix and update fingerprint flashing on herobrine
Date: Mon, 11 Apr 2022 21:00:15 +0000 [thread overview]
Message-ID: <164971081539.4542.965906109471665938.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220317010640.2498502-1-swboyd@chromium.org>
Hello:
This series was applied to qcom/linux.git (for-next)
by Bjorn Andersson <bjorn.andersson@linaro.org>:
On Wed, 16 Mar 2022 18:06:38 -0700 you wrote:
> This series fixes fingerprint pins on herobrine so that the flashing
> code is more reliable. Right now it fails depending on timings. The
> second patch updates the node to be compliant with the new binding
> being proposed.
>
> This technically depends on the binding series[1] but only the second
> patch. The first patch is a fix and should be merged at the earliest
> convenience. Even the second patch could be merged and it would probably
> be OK.
>
> [...]
Here is the summary with links:
- [1/2] arm64: dts: qcom: sc7280-herobrine: Drop outputs on fpmcu pins
https://git.kernel.org/qcom/c/dbcbeed94f3b
- [2/2] arm64: dts: qcom: Fully describe fingerprint node on Herobrine
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-11 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 1:06 [PATCH 0/2] Fix and update fingerprint flashing on herobrine Stephen Boyd
2022-03-17 1:06 ` [PATCH 1/2] arm64: dts: qcom: sc7280-herobrine: Drop outputs on fpmcu pins Stephen Boyd
2022-03-17 21:54 ` Matthias Kaehlcke
2022-03-18 20:50 ` Doug Anderson
2022-03-17 1:06 ` [PATCH 2/2] arm64: dts: qcom: Fully describe fingerprint node on Herobrine Stephen Boyd
2022-03-17 22:06 ` Matthias Kaehlcke
2022-03-17 22:11 ` Stephen Boyd
2022-03-17 22:50 ` Matthias Kaehlcke
2022-03-18 20:55 ` Doug Anderson
2022-03-21 18:53 ` Stephen Boyd
2022-04-11 21:00 ` patchwork-bot+linux-arm-msm [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=164971081539.4542.965906109471665938.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.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.