aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorAlexandru Ardelean <[email protected]>2019-11-05 07:32:12 +0000
committerGreg Kroah-Hartman <[email protected]>2019-11-14 03:49:48 +0000
commit3ec1bd7693ee5bba69eaa1a2b74b14d37971769e (patch)
tree4c1b8f680f608bd641b652e18720ddd087864217 /net/unix/af_unix.c
parentbinder: Handle start==NULL in binder_update_page_range() (diff)
downloadkernel-3ec1bd7693ee5bba69eaa1a2b74b14d37971769e.tar.gz
kernel-3ec1bd7693ee5bba69eaa1a2b74b14d37971769e.zip
uio: fix irq init with dt support & irq not defined
This change also does a bit of a unification for the IRQ init code. But the actual problem is that UIO_IRQ_NONE == 0, so for the DT case where UIO_IRQ_NONE gets assigned to `uioinfo->irq`, a 2nd initialization will get triggered (for the IRQ) and this one will exit via `goto bad1`. As far as things seem to go, the only case where UIO_IRQ_NONE seems valid, is when using a device-tree. The driver has some legacy support for old platform_data structures. It looks like, for platform_data a non-existent IRQ is an invalid case (or was considered an invalid case). Which is why -ENXIO is treated only when a DT is used. Signed-off-by: Dragos Bogdan <[email protected]> Signed-off-by: Alexandru Ardelean <[email protected]> Acked-by: Damian Hobson-Garcia <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions