diff options
| author | Sergey Shtylyov <s.shtylyov@omp.ru> | 2022-03-11 22:35:29 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-04-27 09:51:57 +0200 |
| commit | ce753ad1549cbe9ccaea4c06a1f5fa47432c8289 (patch) | |
| tree | ec1a5b28b9866af9dfb19d25486cb0cc4a4d1ea3 /scripts | |
| parent | a72b6dff4089e6c3455e73ea97b08623b4fed699 (diff) | |
| download | linux-stable-ce753ad1549cbe9ccaea4c06a1f5fa47432c8289.tar.gz linux-stable-ce753ad1549cbe9ccaea4c06a1f5fa47432c8289.tar.bz2 linux-stable-ce753ad1549cbe9ccaea4c06a1f5fa47432c8289.zip | |
platform: finally disallow IRQ0 in platform_get_irq() and its ilk
The commit a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is
invalid") only calls WARN() when IRQ0 is about to be returned, however
using IRQ0 is considered invalid (according to Linus) outside the arch/
code where it's used by the i8253 drivers. Many driver subsystems treat
0 specially (e.g. as an indication of the polling mode by libata), so
the users of platform_get_irq[_byname]() in them would have to filter
out IRQ0 explicitly and this (quite obviously) doesn't scale...
Let's finally get this straight and return -EINVAL instead of IRQ0!
Fixes: a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is invalid")
Acked-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
Link: https://lore.kernel.org/r/025679e1-1f0a-ae4b-4369-01164f691511@omp.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions