public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com, Tsigan@ci.codeaurora.org,
	vladislav.tsigan@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel: Fix the sfi name for BlazarU
Date: Thu, 27 Jun 2024 15:01:05 +0000	[thread overview]
Message-ID: <171950046501.29698.11686044297550018903.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240627130639.2744811-1-kiran.k@intel.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 27 Jun 2024 18:36:39 +0530 you wrote:
> Use INTEL_HW_VARIANT() instead of CNVi Id to decide to load Intermediate
> Loader (IML) image. Fix the driver loading incorrect firmware for
> BlazarU product.
> 
> dmesg:
> .....
> [146.111834] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
> [146.111839] Bluetooth: hci0: Bootloader timestamp 2022.18 buildtype 1 build 16362
> [146.111848] Bluetooth: hci0: No support for _PRR ACPI method
> [146.112204] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0291-0291-iml.sfi (-2)
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btintel: Fix the sfi name for BlazarU
    https://git.kernel.org/bluetooth/bluetooth-next/c/c341bd6acce9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-27 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 13:06 [PATCH v1] Bluetooth: btintel: Fix the sfi name for BlazarU Kiran K
2024-06-27 13:37 ` [v1] " bluez.test.bot
2024-06-27 15:01 ` 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=171950046501.29698.11686044297550018903.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=Tsigan@ci.codeaurora.org \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravishankar.srivatsa@intel.com \
    --cc=vladislav.tsigan@intel.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