[bluez/bluez] 63f1ab: rfkill: Do not log errors for missing device path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 63f1ab560c4253742aa12f139610d5c1c52debb5
      https://github.com/bluez/bluez/commit/63f1ab560c4253742aa12f139610d5c1c52debb5
  Author: Marcus Prebble <marcus.prebble@xxxxxxxx>
  Date:   2024-11-13 (Wed, 13 Nov 2024)

  Changed paths:
    M src/rfkill.c

  Log Message:
  -----------
  rfkill: Do not log errors for missing device path

In the case of our products, we lack a physical RFKILL switch and do
not have the rfkill module enabled in the kernel which resulted in an
error message each time bluetoothd was started.

This commit looks at the errno code after failing to open the RFKILL
device and only logs an error if it is something other than ENOENT
(No such file or directory).

Fixes: https://github.com/bluez/bluez/issues/792



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux