Re: [PATCH v6 39/57] rtc: Remove dev_err() usage after platform_get_irq()

2019-08-13 Thread Alexandre Belloni
On 30/07/2019 11:15:39-0700, Stephen Boyd wrote: > We don't need dev_err() messages when platform_get_irq() fails now that > platform_get_irq() prints an error message itself when something goes > wrong. Let's remove these prints with a simple semantic patch. > > // > @@ > expression ret; >

Re: [PATCH v6 39/57] rtc: Remove dev_err() usage after platform_get_irq()

2019-08-08 Thread Geert Uytterhoeven
Hi Stephen, On Tue, Jul 30, 2019 at 8:21 PM Stephen Boyd wrote: > We don't need dev_err() messages when platform_get_irq() fails now that > platform_get_irq() prints an error message itself when something goes > wrong. Let's remove these prints with a simple semantic patch. > > // > @@ >

[PATCH v6 39/57] rtc: Remove dev_err() usage after platform_get_irq()

2019-07-30 Thread Stephen Boyd
We don't need dev_err() messages when platform_get_irq() fails now that platform_get_irq() prints an error message itself when something goes wrong. Let's remove these prints with a simple semantic patch. // @@ expression ret; struct platform_device *E; @@ ret = ( platform_get_irq(E, ...) |