[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241015045843.20134-1-everestkc@everestkc.com.np>
Date: Mon, 14 Oct 2024 22:58:41 -0600
From: "Everest K.C." <everestkc@...restkc.com.np>
To: marcel@...tmann.org,
luiz.dentz@...il.com
Cc: "Everest K.C." <everestkc@...restkc.com.np>,
skhan@...uxfoundation.org,
kernel-janitors@...r.kernel.org,
linux-bluetooth@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH V2][next] Bluetooth: btintel_pcie: Remove structually deadcode
The switch case statement has a default branch. Thus, the return
statement at the end of the function can never be reached.
Fix it by removing the return statement at the end of the
function.
The intel bluetooth module was successfully built after the change
without any errors.
This issue was reported by Coverity Scan.
https://scan7.scan.coverity.com/#/project-view/51525/11354?selectedIssue=1600709
Fixes: 5ea625845b0f ("Bluetooth: btintel_pcie: Add handshake between driver and firmware")
Signed-off-by: Everest K.C. <everestkc@...restkc.com.np>
---
V1 -> V2: - Changed "Fixing" to "Fix" in the changelog
- Added that the change was successfully built
- Added kernel-janitors mailing list to CC
drivers/bluetooth/btintel_pcie.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index e4ae8c898dfd..660496e55276 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -391,7 +391,6 @@ static inline char *btintel_pcie_alivectxt_state2str(u32 alive_intr_ctxt)
default:
return "unknown";
}
- return "null";
}
/* This function handles the MSI-X interrupt for gp0 cause (bit 0 in
--
2.43.0
Powered by blists - more mailing lists