From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?TWF0ZXVzeiBKb8WEY3p5ayA8bWF0LmpvbmN6eWtAbzIucGw+?=@ci.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, brian.gix@intel.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
johan.hedberg@gmail.com
Subject: Re: [PATCH] Bluetooth: silence a dmesg error message in hci_request.c
Date: Wed, 16 Nov 2022 21:40:15 +0000 [thread overview]
Message-ID: <166863481577.13601.1517745268400800639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116202856.55847-1-mat.jonczyk@o2.pl>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 16 Nov 2022 21:28:56 +0100 you wrote:
> On kernel 6.1-rcX, I have been getting the following dmesg error message
> on every boot, resume from suspend and rfkill unblock of the Bluetooth
> device:
>
> Bluetooth: hci0: HCI_REQ-0xfcf0
>
> After some investigation, it turned out to be caused by
> commit dd50a864ffae ("Bluetooth: Delete unreferenced hci_request code")
> which modified hci_req_add() in net/bluetooth/hci_request.c to always
> print an error message when it is executed. In my case, the function was
> executed by msft_set_filter_enable() in net/bluetooth/msft.c, which
> provides support for Microsoft vendor opcodes.
>
> [...]
Here is the summary with links:
- Bluetooth: silence a dmesg error message in hci_request.c
https://git.kernel.org/bluetooth/bluetooth-next/c/c3fd63f7fe5a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-16 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 20:28 [PATCH] Bluetooth: silence a dmesg error message in hci_request.c Mateusz Jończyk
2022-11-16 21:04 ` bluez.test.bot
2022-11-16 21:40 ` patchwork-bot+bluetooth [this message]
2022-11-27 10:57 ` [PATCH] " Mateusz Jończyk
2022-11-17 20:34 ` Gix, Brian
2022-11-17 21:27 ` Mateusz Jończyk
2022-11-17 21:36 ` Gix, Brian
2022-11-17 22:12 ` Luiz Augusto von Dentz
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=166863481577.13601.1517745268400800639.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?TWF0ZXVzeiBKb8WEY3p5ayA8bWF0LmpvbmN6eWtAbzIucGw+?=@ci.codeaurora.org \
--cc=brian.gix@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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