Files
systemd/src
Lennart Poettering bc5e002ef1 rfkill: treat ENXIO/ENODEV the same way as ENOENT
If an rfkill device disappears between the time we get notified about
the existance and we fully opened it we might get ENXIO or ENODEV (i.e.
the two kinds of "device not found" errors, which are typically
generated when for example a device node has no actual backing device
behind it). let's handle that the same way as ENOENT, and downgrade the
log message to LOG_DEBUG.

Fixes: #8586
2018-04-05 13:00:43 +02:00
..
2018-03-19 21:04:02 +09:00
2018-04-05 14:26:34 +09:00
…
2018-03-22 20:21:42 +01:00
…
2018-03-22 20:30:40 +01:00