Re: [PATCH 2/7] net: fix cpu_max_bits_warn() usage in netif_attrmask_next{,_and}

From: Yury Norov
Date: Mon Sep 26 2022 - 14:05:02 EST


On Mon, Sep 26, 2022 at 10:34:37AM -0700, Jakub Kicinski wrote:
> On Mon, 19 Sep 2022 14:05:54 -0700 Yury Norov wrote:
> > The functions require to be passed with a cpu index prior to one that is
> > the first to start search, so the valid input range is [-1, nr_cpu_ids-1).
> > However, the code checks against [-1, nr_cpu_ids).
>
> Yup, the analysis looks correct:
>
> Acked-by: Jakub Kicinski <kuba@xxxxxxxxxx>

Thanks. If no other comments from you and others, I'll take the series in
bitmap-for-next.