This patch fixes the below warning:
drivers/usb/renesas_usbhs/mod.c: In function 'usbhs_status_get_each_irq':
drivers/usb/renesas_usbhs/mod.c:195:13: warning: variable 'intenb0'
set but not used [-Wunused-but-set-variable]
195 | u16 intenb0, intenb1;
|
Fixes: 33e4245ee919 ("usb: renesas_usbhs: Use platform_get_irq() to get the interrupt")
Reported-by: kernel test robot <redacted>
Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
drivers/usb/renesas_usbhs/mod.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
On Tue, Dec 21, 2021 at 05:15:32PM +0000, Lad Prabhakar wrote:
quoted hunk
This patch fixes the below warning:
drivers/usb/renesas_usbhs/mod.c: In function 'usbhs_status_get_each_irq':
drivers/usb/renesas_usbhs/mod.c:195:13: warning: variable 'intenb0'
set but not used [-Wunused-but-set-variable]
195 | u16 intenb0, intenb1;
|
Fixes: 33e4245ee919 ("usb: renesas_usbhs: Use platform_get_irq() to get the interrupt")
Reported-by: kernel test robot <redacted>
Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
drivers/usb/renesas_usbhs/mod.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Did you just break the hardware? Reading is often times needed and
clang has no idea about hardware issues. We need proof in the changlog
that this really is safe to do.
How did you test your change?
thanks,
greg k-h
Hi Greg,
Thank you for the review.
On Wed, Dec 22, 2021 at 6:10 AM Greg Kroah-Hartman
[off-list ref] wrote:
On Tue, Dec 21, 2021 at 05:15:32PM +0000, Lad Prabhakar wrote:
quoted
This patch fixes the below warning:
drivers/usb/renesas_usbhs/mod.c: In function 'usbhs_status_get_each_irq':
drivers/usb/renesas_usbhs/mod.c:195:13: warning: variable 'intenb0'
set but not used [-Wunused-but-set-variable]
195 | u16 intenb0, intenb1;
|
Fixes: 33e4245ee919 ("usb: renesas_usbhs: Use platform_get_irq() to get the interrupt")
Reported-by: kernel test robot <redacted>
Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
drivers/usb/renesas_usbhs/mod.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Did you just break the hardware? Reading is often times needed and
clang has no idea about hardware issues. We need proof in the changlog
that this really is safe to do.
I introduced this warning in commit 33e4245ee919 ("usb: renesas_usbhs:
Use platform_get_irq() to get the interrupt'') where
IORESOURCE_IRQ_SHAREABLE flag handling was dropped and I missed to
remove this change. As a result I included a fixes tag for this
commit. Let me know if you want me to update the changelog.
On Wed, Dec 22, 2021 at 09:01:03AM +0000, Lad, Prabhakar wrote:
Hi Greg,
Thank you for the review.
On Wed, Dec 22, 2021 at 6:10 AM Greg Kroah-Hartman
[off-list ref] wrote:
quoted
On Tue, Dec 21, 2021 at 05:15:32PM +0000, Lad Prabhakar wrote:
quoted
This patch fixes the below warning:
drivers/usb/renesas_usbhs/mod.c: In function 'usbhs_status_get_each_irq':
drivers/usb/renesas_usbhs/mod.c:195:13: warning: variable 'intenb0'
set but not used [-Wunused-but-set-variable]
195 | u16 intenb0, intenb1;
|
Fixes: 33e4245ee919 ("usb: renesas_usbhs: Use platform_get_irq() to get the interrupt")
Reported-by: kernel test robot <redacted>
Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
drivers/usb/renesas_usbhs/mod.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Did you just break the hardware? Reading is often times needed and
clang has no idea about hardware issues. We need proof in the changlog
that this really is safe to do.
I introduced this warning in commit 33e4245ee919 ("usb: renesas_usbhs:
Use platform_get_irq() to get the interrupt'') where
IORESOURCE_IRQ_SHAREABLE flag handling was dropped and I missed to
remove this change. As a result I included a fixes tag for this
commit. Let me know if you want me to update the changelog.
Yes please explain why this change is ok, not just that it is a random
compiler warning cleanup.