From: patchwork-bot+linux-arm-msm@kernel.org
To: Matthias Kaehlcke <mka@chromium.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 1/2] arm64: dts: qcom: sc7280: Add SAR sensors for herobrine
Date: Mon, 11 Apr 2022 21:00:15 +0000 [thread overview]
Message-ID: <164971081543.4542.2708265985278814513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220329105854.v3.1.Icedb2e3cd5e21f3a4ec535ddf756fa44d053b6ed@changeid>
Hello:
This series was applied to qcom/linux.git (for-next)
by Bjorn Andersson <bjorn.andersson@linaro.org>:
On Tue, 29 Mar 2022 10:59:33 -0700 you wrote:
> Add nodes for the two SX9324 SAR proximity sensors. Not all herobrine
> boards have these sensors, so leave them disabled by default.
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> ---
> Depends on 'arm64: dts: qcom: sc7280: Fix sar1_irq_odl node name' [1] for
> the second SAR sensor to be probed successfully.
>
> [...]
Here is the summary with links:
- [v3,1/2] arm64: dts: qcom: sc7280: Add SAR sensors for herobrine
https://git.kernel.org/qcom/c/70137d1d8a63
- [v3,2/2] arm64: dts: qcom: sc7280: Add device tree for herobrine villager
https://git.kernel.org/qcom/c/ee2a62116015
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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:59 [PATCH v3 1/2] arm64: dts: qcom: sc7280: Add SAR sensors for herobrine Matthias Kaehlcke
2022-03-29 17:59 ` [PATCH v3 2/2] arm64: dts: qcom: sc7280: Add device tree for herobrine villager Matthias Kaehlcke
2022-03-29 18:43 ` [PATCH v3 1/2] arm64: dts: qcom: sc7280: Add SAR sensors for herobrine 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=164971081543.4542.2708265985278814513.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mka@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.