From: patchwork-bot+bluetooth@kernel.org
To: Zhengping Jiang <jiangzp@google.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, johan.hedberg@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/1] Bluetooth: hci_qca: only assign wakeup with serial port support
Date: Thu, 13 Oct 2022 22:30:15 +0000 [thread overview]
Message-ID: <166570021547.5001.4551865478943304906.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221013214508.2195347-1-jiangzp@google.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 13 Oct 2022 14:45:07 -0700 you wrote:
> This patch will check if the serial port supports wakeup before assigning
> the hdev->wakeup callback. After landing the 'commit c1a74160eaf1a
> ("Bluetooth: hci_qca: Add device_may_wakeup support")', the wake-on-bt
> was broken in Jacuzzi because the qca_wakeup returns false. In this case
> it will fall back to the default hci_uart_wakeup.
>
> Changes in v1:
> - Check serial port support before assigning wakeup callback
>
> [...]
Here is the summary with links:
- [v1,1/1] Bluetooth: hci_qca: only assign wakeup with serial port support
https://git.kernel.org/bluetooth/bluetooth-next/c/9fe208c7117d
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-10-13 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 21:45 [PATCH v1 0/1] Bluetooth: hci_qca: only assign wakeup with serial port support Zhengping Jiang
2022-10-13 21:45 ` [PATCH v1 1/1] " Zhengping Jiang
2022-10-13 22:30 ` 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=166570021547.5001.4551865478943304906.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=jiangzp@google.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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