From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
amitkumar.karwar@nxp.com, rohit.fule@nxp.com, yuzhi.jin@nxp.com,
sherry.sun@nxp.com, ziniu.wang_1@nxp.com, haibo.chen@nxp.com,
LnxRevLi@nxp.com
Subject: Re: [PATCH v2 1/2] Bluetooth: btnxpuart: Drop _v0 suffix from FW names
Date: Thu, 26 Sep 2024 20:30:32 +0000 [thread overview]
Message-ID: <172738263200.1385049.5849692333167490001.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240926040757.375999-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 Thu, 26 Sep 2024 09:37:56 +0530 you wrote:
> This updates all FW names by dropping the _v0 suffix.
> Its been decided that all NXP BT/ WiFi FW names won't support _v0 suffix.
> The suffix would be kept for next HW versions such as v1, v2 and so on,
> which do not have backward compatible FW.
>
> This change affects W8987, IW416 and IW615 chipsets, out of which new FW
> files for W8987 and IW615 are yet to be released to broad market.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: btnxpuart: Drop _v0 suffix from FW names
https://git.kernel.org/bluetooth/bluetooth-next/c/0d9899d4df63
- [v2,2/2] Bluetooth: btnxpuart: Rename IW615 to IW610
https://git.kernel.org/bluetooth/bluetooth-next/c/394cf44ded5e
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:[~2024-09-26 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 4:07 [PATCH v2 1/2] Bluetooth: btnxpuart: Drop _v0 suffix from FW names Neeraj Sanjay Kale
2024-09-26 4:07 ` [PATCH v2 2/2] Bluetooth: btnxpuart: Rename IW615 to IW610 Neeraj Sanjay Kale
2024-09-26 20: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=172738263200.1385049.5849692333167490001.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=LnxRevLi@nxp.com \
--cc=amitkumar.karwar@nxp.com \
--cc=haibo.chen@nxp.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 \
--cc=yuzhi.jin@nxp.com \
--cc=ziniu.wang_1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox