aboutsummaryrefslogtreecommitdiff
path: root/sys/crypto/sha2/sha256c.c
diff options
context:
space:
mode:
authorBjoern A. Zeeb <bz@FreeBSD.org>2026-10-19 21:30:14 +0000
committerBjoern A. Zeeb <bz@FreeBSD.org>2026-10-20 22:50:14 +0000
commitd2145e9b96448da34d3cfede24c509af6d830c92 (patch)
treeea203c6e3382b0ecf323489513e98e5f65b4b0eb /sys/crypto/sha2/sha256c.c
parent06abe08de45d251410949eac1bbb025367275260 (diff)
LinuxKPI: restore several hard coded return values for the CONFIG_PM caseHEADmain
drm-kmod sets CONFIG_PM (unclear if for other parts) but LinuxKPI has no understanding of a dev->power implementation for pm_runtime.h. The return values based on !CONFIG_PM thus cause problems to drm-kmod. Return the previous values under CONFIG_PM but leave the TODO logging as the actual implementation is missing and return values may not be universally correct (beyond the known drm-kmod use cases). The following functions having a return value but none sepcific for CONFIG_PM as (based on drm-kmod master): pm_runtime_resume only caller ignores the return value pm_runtime_set_active two callers ignore the return value pm_runtime_put_autosuspend all callers seem to ignore the return value pm_runtime_autosuspend 2/3 callers ignore the return value; 3rd is #ifdef __linux__ pm_runtime_suspended 3/4 callers ... do check the return value but the logic expects the false, which also matches the previous value. Fixes: 863fe7ae5152 ("LinuxKPI: re-implement pm_runtime.h") Reported by: markj MFC after: 3 days Tested by: markj, Oleg V. Nauman (oleg.nauman gmail.com) Differential Revision: https://reviews.freebsd.org/D60878
Diffstat (limited to 'sys/crypto/sha2/sha256c.c')
0 files changed, 0 insertions, 0 deletions