From: patchwork-bot+bluetooth@kernel.org
To: Takashi Iwai <tiwai@suse.de>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btmtk: Add MODULE_FIRMWARE() for MT7922
Date: Mon, 04 Mar 2024 21:30:27 +0000 [thread overview]
Message-ID: <170958782730.29902.5440375216953533108.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227102914.8341-1-tiwai@suse.de>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 27 Feb 2024 11:29:14 +0100 you wrote:
> Since dracut refers to the module info for defining the required
> firmware files and btmtk driver doesn't provide the firmware info for
> MT7922, the generate initrd misses the firmware, resulting in the
> broken Bluetooth.
>
> This patch simply adds the MODULE_FIRMWARE() for the missing entry
> for covering that.
>
> [...]
Here is the summary with links:
- Bluetooth: btmtk: Add MODULE_FIRMWARE() for MT7922
https://git.kernel.org/bluetooth/bluetooth-next/c/aa1767a3fcd7
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-03-04 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 10:29 [PATCH] Bluetooth: btmtk: Add MODULE_FIRMWARE() for MT7922 Takashi Iwai
2024-02-27 10:40 ` Paul Menzel
2024-02-27 10:57 ` bluez.test.bot
2024-02-29 17:27 ` [PATCH] " Matthias Brugger
2024-03-04 21: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=170958782730.29902.5440375216953533108.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthias.bgg@gmail.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).