From: patchwork-bot+chrome-platform@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
chrome-platform@lists.linux.dev, groeck@chromium.org,
dianders@chromium.org, hesling@chromium.org,
tomhughes@chromium.org, amstan@chromium.org, tzungbi@kernel.org,
mka@chromium.org, bleung@chromium.org, lee.jones@linaro.org
Subject: Re: [PATCH v5 0/3] dt-bindings: cros-ec: Update for fingerprint devices
Date: Mon, 06 Jun 2022 03:33:49 +0000 [thread overview]
Message-ID: <165448642983.20111.12412315955580522831.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220512013921.164637-1-swboyd@chromium.org>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Lee Jones <lee.jones@linaro.org>:
On Wed, 11 May 2022 18:39:18 -0700 you wrote:
> This patch series introduces a DT binding for chromeos fingerprint
> devices. The first two patches tighten up the existing binding and the
> final patch introduces the fingerprint binding. As there aren't any
> driver patches this can probably go directly through the DT binding tree
> if Lee can ack the patches. Or go through mfd tree if DT maintainers
> ack/review.
>
> [...]
Here is the summary with links:
- [v5,1/3] dt-bindings: cros-ec: Fix a typo in description
https://git.kernel.org/chrome-platform/c/f93afd8e7567
- [v5,2/3] dt-bindings: cros-ec: Reorganize property availability
(no matching commit)
- [v5,3/3] dt-bindings: cros-ec: Add ChromeOS fingerprint binding
(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-06-06 3:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 1:39 [PATCH v5 0/3] dt-bindings: cros-ec: Update for fingerprint devices Stephen Boyd
2022-05-12 1:39 ` [PATCH v5 1/3] dt-bindings: cros-ec: Fix a typo in description Stephen Boyd
2022-05-12 15:20 ` Guenter Roeck
2022-05-16 15:15 ` Rob Herring
2022-05-23 15:11 ` Lee Jones
2022-05-12 1:39 ` [PATCH v5 2/3] dt-bindings: cros-ec: Reorganize property availability Stephen Boyd
2022-05-12 23:44 ` Doug Anderson
2022-05-16 19:32 ` Stephen Boyd
2022-05-16 15:20 ` Rob Herring
2022-05-12 1:39 ` [PATCH v5 3/3] dt-bindings: cros-ec: Add ChromeOS fingerprint binding Stephen Boyd
2022-05-12 23:44 ` Doug Anderson
2022-05-16 15:20 ` Rob Herring
2022-05-16 19:23 ` Stephen Boyd
2022-05-18 16:13 ` Rob Herring
2022-05-18 19:56 ` Stephen Boyd
2022-05-19 19:48 ` Rob Herring
2022-06-06 3:33 ` patchwork-bot+chrome-platform [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=165448642983.20111.12412315955580522831.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=amstan@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=hesling@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=tomhughes@chromium.org \
--cc=tzungbi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).