On 01.03.2021 09:27, Jan Beulich wrote: > While we've long done away with CONFIG_SMP, we still allow > CONFIG_NR_CPUS to be set to 1. Hence at least randconfig builds > may fail, and the first of the two issues addressed was actually > observed in the RISC-V bring-up work. I didn't check whether Arm > would also have issues like these. > > 1: sched: fix build when NR_CPUS == 1 > 2: x86: fix build when NR_CPUS == 1
I've tagged this with a question mark because on one hand such configurations are unusual and hence unlikely to be overly relevant for the release. Otoh randconfig failures would better be avoided. Jan
