On Thu, Sep 10, 2026 at 08:00:39PM +0100, Mark Brown wrote: > When we refuse to change the GCS configuraiton due to locking we > currently return -EBUSY which is an odd choice. The only userspace I > found that relies on this value at present is the kselftest and other > architectures are using the more obvious -EPERM here let's switch.
IIUC, riscv is returning -EINVAL. Should we get an overall consistent value? Personally I find -EBUSY quite descriptive but I don't mind aligning the architectures (before user space starts making use of the return value). -- Catalin
