summaryrefslogtreecommitdiff
path: root/include/linux/byteorder
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2025-12-22 21:25:57 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2026-01-08 21:36:51 +0100
commit01eafccacc707da2db2a9eb4be56c9367e42323f (patch)
tree54373cb54510b3a2570d47879cf6890caa81a4d5 /include/linux/byteorder
parentd33976be6cecfe340a52b365ecf706a0c55d543d (diff)
coresight: Discard pm_runtime_put() return values
Failing a debugfs write due to pm_runtime_put() returning a negative value is not particularly useful. Returning an error code from pm_runtime_put() merely means that it has not queued up a work item to check whether or not the device can be suspended and there are many perfectly valid situations in which that can happen, like after writing "on" to the devices' runtime PM "control" attribute in sysfs for one example. It also happens when the kernel has been configured with CONFIG_PM unset, in which case debug_disable_func() in the coresight driver will always return an error. For this reason, update debug_disable_func() to simply discard the return value of pm_runtime_put(), change its return type to void, and propagate that change to debug_func_knob_write(). This will facilitate a planned change of the pm_runtime_put() return type to void in the future. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com> Link: https://patch.msgid.link/2058657.yKVeVyVuyW@rafael.j.wysocki
Diffstat (limited to 'include/linux/byteorder')
0 files changed, 0 insertions, 0 deletions