From: Mark Brown <broonie@kernel•org>
To: Frederic Weisbecker <frederic@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure in final build
Date: Fri, 27 Mar 2026 22:01:06 +0000 [thread overview]
Message-ID: <acb-IuZ4vDkwwQLW@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
Hi all,
After merging the kthread tree, 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel•org>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure in final build
Date: Fri, 27 Mar 2026 22:03:39 +0000 [thread overview]
Message-ID: <acb-IuZ4vDkwwQLW@sirena.co.uk> (raw)
Message-ID: <20260327220339.O-zTDQTzxTVZuOedEur2L-0-IcuY33iAPnsEEUtrARo@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-27 22:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 22:01 Mark Brown [this message]
2026-03-27 22:03 ` linux-next: build failure in final build Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
-- 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=acb-IuZ4vDkwwQLW@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=frederic@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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