On 10-10-24, 13:08, Beata Michalska wrote: > That is a fair point but I am not entirely convinced using '0' instead makes > things any more clearer as this is in no way a valid CPU frequency. > As long as we document the expected behaviour keeping the interface well > defined, both options should be fine I guess. > > @Viresh: what is your opinion on that one ? Failing to get frequency for the CPU shouldn't be represented by 0, even if it is confusing for the user. -- viresh
