[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200311.230402.1496009558967017193.davem@davemloft.net>
Date: Wed, 11 Mar 2020 23:04:02 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mklntf@...il.com
Cc: peppe.cavallaro@...com, alexandre.torgue@...com,
joabreu@...opsys.com, mcoquelin.stm32@...il.com,
netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: stmmac: platform: Fix misleading interrupt error
msg
From: Markus Fuchs <mklntf@...il.com>
Date: Fri, 6 Mar 2020 17:38:48 +0100
> Not every stmmac based platform makes use of the eth_wake_irq or eth_lpi
> interrupts. Use the platform_get_irq_byname_optional variant for these
> interrupts, so no error message is displayed, if they can't be found.
> Rather print an information to hint something might be wrong to assist
> debugging on platforms which use these interrupts.
>
> Signed-off-by: Markus Fuchs <mklntf@...il.com>
What do you mean the error message is misleading right now?
It isn't printing anything out at the moment in this situation.
Powered by blists - more mailing lists