On Tue, Aug 13, 2024 at 07:02:20PM +0300, Andy Shevchenko wrote: > 0 is incorrect error code when failed to parse and map IRQ. > Replace OF specific old API for IRQ retrieval with a generic > one to fix this issue. Scratch it, it has the same issue and it seems it predates the mentioned patch as we need to return a real error code. -- With Best Regards, Andy Shevchenko
Re: [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
- From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
- Date: Tue, 13 Aug 2024 21:29:11 +0300
- In-reply-to: <20240813160220.2357338-1-andriy.shevchenko@linux.intel.com>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20240813160220.2357338-1-andriy.shevchenko@linux.intel.com>
- References:
- [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
- From: Andy Shevchenko
- [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
- Prev by Date: [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
- Next by Date: Re: [PATCH v2 1/1] spi: dt-bindings: convert spi-sc18is602.txt to yaml format
- Previous by thread: [PATCH v1 1/1] spi: ppc4xx: Avoid returning 0 when failed to parse and map IRQ
- Index(es):
 |