Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 22 Jul 2022 12:29:27 -0700
From:   Yury Norov <yury.norov@gmail.com>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the bitmap tree
Message-ID: <Ytr6l2CHG8lbU+8Z@yury-laptop>
References: <20220722191657.1d7282c2@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220722191657.1d7282c2@canb.auug.org.au>
Precedence: bulk

On Fri, Jul 22, 2022 at 07:16:57PM +1000, Stephen Rothwell wrote:
> Hi all,
 ...

> I am not sure which commit caused this.  Though I suspect
> 
>   bbe8fb1a3c53 ("lib/nodemask: inline next_node_in() and node_random()")
> 
> which added the include of random.h to nodemask.h
> 
> I have used the bitmap tree from next-20220721 for today.

Hi Stephen,

You're right. The problem in the last patch of the series. I've got
the fix already, and testing it now.

I'll drop the bbe8fb1a3c53 and submit it separately together with
header fix.

Thanks,
Yury