Received-SPF: pass (google.com: domain of linux-kernel+bounces-173890-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Wed, 8 May 2024 15:18:48 -0700
From: Yury Norov <yury.norov@gmail.com>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: <Zjv6SCS6WSCHbTGR@yury-ThinkPad>
References: <20240508162755.7d339509@canb.auug.org.au>
 <Zjt9GRTRgjfgtOwd@visitorckw-System-Product-Name>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Zjt9GRTRgjfgtOwd@visitorckw-System-Product-Name>

On Wed, May 08, 2024 at 09:24:41PM +0800, Kuan-Wei Chiu wrote:
> On Wed, May 08, 2024 at 04:27:55PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the bitmap tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > lib/test_bitops.c: In function 'test_fns':
> > lib/test_bitops.c:56:9: error: cleanup argument not a function
> >    56 |         unsigned long *buf __free(kfree) = NULL;
> >       |         ^~~~~~~~
> > lib/test_bitops.c:60:15: error: implicit declaration of function 'kmalloc_array' [-Werror=implicit-function-declaration]
> >    60 |         buf = kmalloc_array(10000, sizeof(unsigned long), GFP_KERNEL);
> >       |               ^~~~~~~~~~~~~
> > lib/test_bitops.c:60:13: error: assignment to 'long unsigned int *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
> >    60 |         buf = kmalloc_array(10000, sizeof(unsigned long), GFP_KERNEL);
> >       |             ^
> > cc1: all warnings being treated as errors
> > 
> > Caused by commit
> > 
> >   777c893e12fa ("lib/test_bitops: Add benchmark test for fns()")
> >
> > I have used the bitmap tree from next-20240507 for today.
> > 
> > -- 
> > Cheers,
> > Stephen Rothwell
> 
> Hi Yury,
> 
> I believe the following patch can resolve this issue. If you agree that
> this patch is correct, could you help me fold it into the commit that
> caused the error mentioned above?
> 
> Regards,
> Kuan-Wei

Updated, thanks