From: patchwork-bot+bluetooth@kernel.org
To: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
quic_bgodavar@quicinc.com, quic_rjliao@quicinc.com,
quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
quic_anubhavg@quicinc.com, linux-bluetooth@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/1] Enable Bluetooth on qcs6490-rb3gen2 board
Date: Thu, 09 Jan 2025 16:17:06 +0000 [thread overview]
Message-ID: <173643942698.1375203.6019531201019539280.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250107134157.211702-1-quic_janathot@quicinc.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 7 Jan 2025 19:11:56 +0530 you wrote:
> - Patch 1/1 Utilize the PMU abstraction for the WCN6750 and update the bindings accordingly.
>
> ----
> Changes from v6:
> * Elaborated the commit message with more information.
> * Link to v6: https://lore.kernel.org/lkml/20241223135700.22660-1-quic_janathot@quicinc.com/
>
> [...]
Here is the summary with links:
- [v7,1/1] dt-bindings: bluetooth: Utilize PMU abstraction for WCN6750
https://git.kernel.org/bluetooth/bluetooth-next/c/7e99441aa705
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:[~2025-01-09 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 13:41 [PATCH v7 0/1] Enable Bluetooth on qcs6490-rb3gen2 board Janaki Ramaiah Thota
2025-01-07 13:41 ` [PATCH v7 1/1] dt-bindings: bluetooth: Utilize PMU abstraction for WCN6750 Janaki Ramaiah Thota
2025-01-08 8:00 ` Krzysztof Kozlowski
2025-01-09 16:17 ` patchwork-bot+bluetooth [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=173643942698.1375203.6019531201019539280.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_janathot@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--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