All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 8 May 2024 15:18:48 -0700	[thread overview]
Message-ID: <Zjv6SCS6WSCHbTGR@yury-ThinkPad> (raw)
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

  reply	other threads:[~2024-05-08 22:18 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  6:27 linux-next: build failure after merge of the bitmap tree Stephen Rothwell
2024-05-08 13:24 ` Kuan-Wei Chiu
2024-05-08 22:18   ` Yury Norov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-30  9:11 Thierry Reding
2026-03-24 15:11 Mark Brown
2026-03-24 17:56 ` Yury Norov
2025-11-25  7:24 Stephen Rothwell
2025-11-25  8:05 ` Geert Uytterhoeven
2025-11-25  8:31   ` Miquel Raynal
2025-11-25  8:37     ` Geert Uytterhoeven
2025-11-25 14:44       ` Yury Norov
2025-11-25 14:55         ` Miquel Raynal
2025-11-25  8:53     ` Miquel Raynal
2025-11-28  8:17   ` Miquel Raynal
2025-02-18  5:07 Stephen Rothwell
2025-02-18 10:35 ` Beata Michalska
2025-02-18 13:49   ` Stephen Rothwell
2025-02-18 14:10     ` Catalin Marinas
2025-02-18 14:16       ` Yury Norov
2025-02-18 18:23         ` Catalin Marinas
2025-02-18 19:28           ` Beata Michalska
2025-02-18 19:44             ` Catalin Marinas
2023-10-20  4:49 Stephen Rothwell
2023-10-19  6:01 Stephen Rothwell
2023-10-19 15:58 ` Yury Norov
2023-10-20  4:24   ` Yury Norov
2023-10-20  4:51     ` Stephen Rothwell
2023-10-20 12:33       ` Yury Norov
2023-11-02 11:41         ` Alexander Lobakin
2022-09-26 23:53 broonie
2022-09-27  0:37 ` Yury Norov
2022-09-27 18:56   ` Mark Brown
2022-09-20  8:08 Stephen Rothwell
2022-09-20 14:49 ` Yury Norov
2022-07-27 10:29 Stephen Rothwell
2022-07-22  9:16 Stephen Rothwell
2022-07-22 19:29 ` Yury Norov
2022-07-15 10:29 Stephen Rothwell
2022-07-15 10:29 ` Stephen Rothwell
2022-07-08  7:47 Stephen Rothwell
2022-05-02  8:15 Stephen Rothwell
2022-04-19  4:29 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zjv6SCS6WSCHbTGR@yury-ThinkPad \
    --to=yury.norov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=visitorckw@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.