Since commit a85a6c86c25b ("driver core: platform: Clarify that
IRQ 0 is invalid"), there is no possible both for platform_get_irq()
to return 0.
And the return value of platform_get_irq() is more sensible
to show the error reason.
Since commit 2043727c2882 ("driver core: platform: Make use of
the helper function dev_err_probe()"), there is no need to call
the dev_warn() function directly to print a custom message when
handling an error from platform_get_irq() function as
it is going to display an appropriate error message
in case of a failure.
Ruan Jinjie (2):
rtc: omap: Do not check for 0 return after calling platform_get_irq()
rtc: tps65910: Remove redundant dev_warn() and do not check for 0
return after calling platform_get_irq()
drivers/rtc/rtc-omap.c | 8 ++++----
drivers/rtc/rtc-tps65910.c | 7 ++-----
2 files changed, 6 insertions(+), 9 deletions(-)
--
2.34.1
