All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Brown <broonie@kernel.org>
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 in final build
Date: Fri, 27 Mar 2026 22:18:20 -0400	[thread overview]
Message-ID: <20260327221820.380c19bd@robin> (raw)
In-Reply-To: <acb-IuZ4vDkwwQLW@sirena.co.uk>

On Fri, 27 Mar 2026 22:03:39 +0000
Mark Brown <broonie@kernel.org> wrote:

> Hi all,
> 
> In the final build, today's linux-next build (i386 defconfig) failed
> like this:
> 
> /tmp/next/build/kernel/trace/trace.c:820:5: error: no previous prototype for 'tracing_alloc_snapshot' [-Werror=missing-prototypes]
>   820 | int tracing_alloc_snapshot(void)
>       |     ^~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   bade44fe546212 (tracing: Move snapshot code out of trace.c and into trace_snapshot.c)
>    
> I've left this for today.

Thanks, I'll take a look.

-- Steve

  parent reply	other threads:[~2026-03-28  2:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 22:01 linux-next: build failure in final build Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28  2:18 ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06   ` Linus Torvalds
2026-04-01 14:07 Mark Brown
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32   ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20  8:36   ` Alice Ryhl
2026-01-20 10:01     ` Danilo Krummrich

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=20260327221820.380c19bd@robin \
    --to=rostedt@goodmis.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.