Skip to contentSkip to conversation

Fix unsigned int compared against 0

PATCH In review Advait Dhamorikar 2 participants 3 messages Oct 4, 2024 – Oct 5, 2024

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Fix unsigned int compared against 0

An unsigned value held by offset can never be
negative, so this test will always evaluate
the same way and is therefore redundant.

---
 sound/soc/codecs/tlv320adc3xxx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/tlv320adc3xxx.c +1 -1
index 7073b9d1cda8..868e8a91e05b 100644
@@ -961,7 +961,7 @@ static int adc3xxx_gpio_request(struct gpio_chip *chip, unsigned int offset)
 	if (offset >= ADC3XXX_GPIOS_MAX)
 		return -EINVAL;
 
-	if (offset >= 0 && offset < ADC3XXX_GPIO_PINS) {
+	if (offset < ADC3XXX_GPIO_PINS) {
 		/* GPIO1 is offset 0, GPIO2 is offset 1 */
 		/* We check here that the GPIO pins are either not configured
 		 * in the DT, or that they purposely are set as outputs.
Signature · 1 line
2.34.1
maintainer
#1 lore raw
Quoted 3 lines · Advait Dhamorikar

An unsigned value held by offset can never be
negative, so this test will always evaluate
the same way and is therefore redundant.

Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.

maintainer
#2 lore raw
In reply to Advait Dhamorikar
Quoted 5 lines · Advait Dhamorikar

An unsigned value held by offset can never be
negative, so this test will always evaluate
the same way and is therefore redundant.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] Fix unsigned int compared against 0

      commit: 40ba40fa4e054c62507026454529e3d530e10456

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark