public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Yonghong Song <yonghong.song@linux.dev>,
	Nathan Chancellor <nathan@kernel.org>,
	KBuild Mailing List <linux-kbuild@vger.kernel.org>,
	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 kbuild tree
Date: Mon, 16 Mar 2026 18:56:29 +0100	[thread overview]
Message-ID: <abhETba3IvIH1BU9@levanger> (raw)
In-Reply-To: <d9a3537a-9abc-49f0-86df-13089ff35a3a@sirena.org.uk>

On Mon, Mar 16, 2026 at 05:42:17PM +0000, Mark Brown wrote:
> On Mon, Mar 16, 2026 at 05:02:15PM +0100, Nicolas Schier wrote:
> > On Mon, Mar 16, 2026 at 02:18:45PM +0000, Mark Brown wrote:
> 
> > > Makefile:2254: *** extraneous 'endif'.  Stop.
> > > Makefile:2254: *** extraneous 'endif'.  Stop.
> > >   PERF_VERSION = .gbc1f864a1976
> > > 52.34user 4.91system 0:56.88elapsed 100%CPU (0avgtext+0avgdata 140840maxresident)k
> > > 0inputs+0outputs (0major+1379795minor)pagefaults 0swaps
> > > Building: arm64 allnoconfig
> > > Makefile:2254: *** extraneous 'endif'.  Stop.
> 
> > thanks for the report.  Unfortunately, I cannot reproduce that anyhow;
> > but I pushed to kbuild/kbuild-for-next at 12:36 UTC, might that have
> > been a bad point in time?  Do you have your merge somewhere around where
> > I can fetch it for investigation?
> 
> I tend to start late mornings UTC so something in the middle of the
> night won't be noticed.  I don't have my merge to hand, sorry - you'll
> be able to see where I merged things by looking at the history of -next
> for the kbuild merge when I publish today's -next.  IIRC there as
> nothing other than merges and the commit I flagged in there, it's
> possibly a merge issue with Linus' tree?

Ok, thanks!  Then I'll have a look at it tomorrow (14h ahead) and hope
to fix it for the next '-next' round.

-- 
Nicolas

  reply	other threads:[~2026-03-16 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 14:18 linux-next: build failure after merge of the kbuild tree Mark Brown
2026-03-16 16:02 ` Nicolas Schier
2026-03-16 16:16   ` Yonghong Song
2026-03-16 17:42   ` Mark Brown
2026-03-16 17:56     ` Nicolas Schier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  4:01 Stephen Rothwell
2025-08-18  4:27 ` Nathan Chancellor
2016-09-15  6:08 Stephen Rothwell
2016-09-22 12:52 ` Michal Marek
     [not found] <20110420082514.a9ec4d68.sfr@canb.auug.org.au>
2011-04-20 13:50 ` Michal Marek

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=abhETba3IvIH1BU9@levanger \
    --to=nsc@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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