public inbox for linux-sparse@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: hang with current sparse with upstream linux arm64 build
Date: Mon, 23 Feb 2026 17:20:13 +0000	[thread overview]
Message-ID: <f41dd0af-2b47-420e-8999-0d4149ea4a60@opensource.cirrus.com> (raw)
In-Reply-To: <CAHk-=wijD-giccF6sJ+BdJpGDX9kPEUT6kryaQG0GRyJ3QQwng@mail.gmail.com>

On 23/02/2026 4:43 pm, Linus Torvalds wrote:
> [ I should read all my emails before answering them, but I get too
> much, so here's a second answer just to make sure Ben and Richard see
> my first one in case they don't read the mailing list religiously ]
> 
> On Mon, 23 Feb 2026 at 06:08, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>>>
>> So currently it seems to be hanging when checking drivers/clk/clk.c
>> doing the following.
>>
>> $ make C=1 drivers/clk/clk.o
>>
>> This is working under v6.19 and not under v7.0-rc1
>>
>> The git bisect is pointing to commit e19e1b480ac7 ("add default_gfp()
>> helper macro and use it in the new *alloc_obj() helpers"
> 
> So I think sparse should learn __VA_OPT__, but in the meantime, does
> this attached kernel patch fix it for you?
> 
> It seems to work in my tree, but I haven't actually done anything but
> a very quick build test.
> 
>                 Linus

Only tested with a single (Debian) X86_64 config.
Builds and boots ok.

      reply	other threads:[~2026-02-23 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 10:51 hang with current sparse with upstream linux arm64 build Ben Dooks
2026-02-23 14:07 ` Ben Dooks
2026-02-23 14:46   ` Richard Fitzgerald
2026-02-23 16:43   ` Linus Torvalds
2026-02-23 17:20     ` Richard Fitzgerald [this message]

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=f41dd0af-2b47-420e-8999-0d4149ea4a60@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=ben.dooks@codethink.co.uk \
    --cc=linux-sparse@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox