From: patchwork-bot+bluetooth@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: amitkumar.karwar@nxp.com, neeraj.sanjaykale@nxp.com,
marcel@holtmann.org, luiz.dentz@gmail.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] Bluetooth: btnxpuart: Fix missing devm_request_irq() return value check
Date: Tue, 27 May 2025 13:20:30 +0000 [thread overview]
Message-ID: <174835203049.1634553.7692124762265533667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250525190020.27286-2-krzysztof.kozlowski@linaro.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 25 May 2025 21:00:21 +0200 you wrote:
> Return value of devm_request_irq() must be checked (function is even
> annotated) and without it clang W=1 complains:
>
> btnxpuart.c:494:6: error: unused variable 'ret' [-Werror,-Wunused-variable]
>
> Setting up wakeup IRQ handler is not really critical, because the
> handler is empty, so just log the informational message so user could
> submit proper bug report and silences the clang warning.
>
> [...]
Here is the summary with links:
- Bluetooth: btnxpuart: Fix missing devm_request_irq() return value check
https://git.kernel.org/bluetooth/bluetooth-next/c/4e221e2b5ee0
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:[~2025-05-27 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 19:00 [PATCH] Bluetooth: btnxpuart: Fix missing devm_request_irq() return value check Krzysztof Kozlowski
2025-05-25 19:30 ` bluez.test.bot
2025-05-26 7:23 ` [PATCH] " Neeraj Sanjay Kale
2025-05-27 13:20 ` 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=174835203049.1634553.7692124762265533667.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=justinstitt@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=nick.desaulniers+lkml@gmail.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