spi: spi-mpc512x-psc: Fix an unsigned comparison that can never be negative
PATCH v2 1/1 spi: spi-mpc512x-psc: Fix an unsigned comparison that can never be negative
From: Rajeshwar R Shinde <[email protected]>
In struct mpc512x_psc_spi, the variable 'irq' is declared as an unsigned int. The comparison of variable 'irq' with signed int operand is incorrect. Also, the return value from the call to platform_get_irq(pdev,0) is int and it is assigned to an unsigned int variable 'irq', thus redeclaring the type of variable 'irq' to signed int.
This fixes warning such as:
drivers/spi/spi-mpc512x-psc.c:493:5-13:
WARNING: Unsigned expression compared with zero: mps -> irq < 0
---v1->v2
changed the commit message
--- drivers/spi/spi-mpc512x-psc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-mpc512x-psc.c +1 -1
@@ -53,7 +53,7 @@ struct mpc512x_psc_spi {int type;void __iomem *psc;struct mpc512x_psc_fifo __iomem *fifo; -unsigned int irq; +int irq;u8 bits_per_word;u32 mclk_rate;
Signature · 6 lines
2.25.1 _______________________________________________ Linux-kernel-mentees mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Please verify this patch.
Thanks & Regards
Quoted 39 lines · On Sun, 13 Aug, 2023, 7:42 pm , <[email protected]> wrote:
From: Rajeshwar R Shinde <[email protected]>
In struct
mpc512x_psc_spi, the variable 'irq' is declared as an unsigned int.
The comparison of variable 'irq' with signed int operand is incorrect. Also,
the return value from the call toplatform_get_irq(pdev,0)is int and it is
assigned to an unsigned int variable 'irq', thus redeclaring the type of variable 'irq' to signed int.This fixes warning such as:
drivers/spi/spi-mpc512x-psc.c:493:5-13:
WARNING: Unsigned expression compared with zero: mps -> irq < 0Signed-off-by Rajeshwar R Shinde <[email protected]>---
v1->v2
changed the commit message--- drivers/spi/spi-mpc512x-psc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/spi/spi-mpc512x-psc.c +1
-2@@ -53,7 +53,7 @@ struct mpc512x_psc_spi {int type;void __iomem *psc;struct mpc512x_psc_fifo __iomem *fifo; -unsigned int irq; +int irq;u8 bits_per_word;u32 mclk_rate; --
Quoted 3 lines
2.25.1
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Mark Brown
maintainerQuoted 2 lines · Rajeshwar Shinde
Please verify this patch.
Thanks & Regards
Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed.
Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being addressed.
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Remainder
Quoted 17 lines · Mark Brown,
Quoted 2 lines · Rajeshwar Shinde
Please verify this patch.
Thanks & RegardsPlease don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed.
Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
Quoted 5 lines
Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being addressed.
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Mark Brown
maintainerQuoted 1 line · Rajeshwar Shinde
Remainder
Please read the mail you are replying to...
Quoted 24 lines · Mark Brown,
Quoted 23 lines · Rajeshwar Shinde
Quoted 2 lines
Please verify this patch.
Thanks & RegardsPlease don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed.
Sending content free pings adds to the mail volume (if they are seen at all) which is often the problem and since they can't be reviewed directly if something has gone wrong you'll have to resend the patches anyway, so sending again is generally a better approach though there are some other maintainers who like them - if in doubt look at how patches for the subsystem are normally handled.
Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being addressed.
A message that is not in the archive (sent off-list or not yet received): CA+VNjV3_JRvhjanLEdYRnxcTZv2pv307utD-bpmy_7QFT3Y+Pg@mail.gmail.com
Mark Brown
maintainerQuoted 1 line · Rajeshwar Shinde
Remainder
Seriously, please read and act on what I'm writing.