From: patchwork-bot+bluetooth@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: pavel@ucw.cz, lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jacek.anaszewski@gmail.com,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2] dt-bindings: leds: Document Bluetooth and WLAN triggers
Date: Tue, 24 Jan 2023 23:40:39 +0000 [thread overview]
Message-ID: <167460363944.4058.4676712965831302643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <0d0de1bc949d24e08174205c13c0b59bd73c1ea8.1674384302.git.geert+renesas@glider.be>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 22 Jan 2023 11:47:27 +0100 you wrote:
> Add the missing trigger patterns for Bluetooth and WLAN activity, which
> are already in active use.
>
> While at it, move the mmc pattern comment where it belongs, and restore
> alphabetical sort order.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
> [...]
Here is the summary with links:
- [v2] dt-bindings: leds: Document Bluetooth and WLAN triggers
https://git.kernel.org/bluetooth/bluetooth-next/c/ef017002b93b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-24 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 10:47 [PATCH v2] dt-bindings: leds: Document Bluetooth and WLAN triggers Geert Uytterhoeven
2023-01-24 23:40 ` patchwork-bot+bluetooth [this message]
2023-01-25 15:12 ` Lee Jones
2023-01-25 19:23 ` Luiz Augusto von Dentz
2023-01-26 8:00 ` Lee Jones
2023-01-26 20:46 ` Luiz Augusto von Dentz
2023-01-27 8:47 ` Krzysztof Kozlowski
2023-01-27 9:27 ` Lee Jones
2023-01-26 10:01 ` Krzysztof Kozlowski
2023-01-26 8:01 ` Lee Jones
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=167460363944.4058.4676712965831302643.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=robh@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