From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, amitkumar.karwar@nxp.com,
rohit.fule@nxp.com, sherry.sun@nxp.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Bluetooth: btnxpuart: Add support for IW624 chipset
Date: Wed, 16 Aug 2023 00:10:27 +0000 [thread overview]
Message-ID: <169214462789.26309.9496972962553175060.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230811101232.844769-1-neeraj.sanjaykale@nxp.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 11 Aug 2023 15:42:30 +0530 you wrote:
> This patch series adds support for IW624 in btnxpuart driver.
>
> The first patch removes check for CTS low after FW downloaded as
> it was found to be redundant. It increases the delay from 1000msec
> to 1200msec after FW download as IW624 requires more time to complete
> FW initialization.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: btnxpuart: Remove check for CTS low after FW download
https://git.kernel.org/bluetooth/bluetooth-next/c/8f24666933f1
- [v2,2/2] Bluetooth: btnxpuart: Add support for IW624 chipset
https://git.kernel.org/bluetooth/bluetooth-next/c/f6b00a4fae83
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:[~2023-08-16 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 10:12 [PATCH v2 0/2] Bluetooth: btnxpuart: Add support for IW624 chipset Neeraj Sanjay Kale
2023-08-11 10:12 ` [PATCH v2 1/2] Bluetooth: btnxpuart: Remove check for CTS low after FW download Neeraj Sanjay Kale
2023-08-11 11:04 ` Bluetooth: btnxpuart: Add support for IW624 chipset bluez.test.bot
2023-08-11 10:12 ` [PATCH v2 2/2] " Neeraj Sanjay Kale
2023-08-16 0:10 ` 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=169214462789.26309.9496972962553175060.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.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 \
--cc=neeraj.sanjaykale@nxp.com \
--cc=rohit.fule@nxp.com \
--cc=sherry.sun@nxp.com \
/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.