From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the mm-nonmm-unstable tree
Date: Fri, 11 Jul 2025 10:58:04 +1000 [thread overview]
Message-ID: <20250711105804.3447e832@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi all,
After merging the mm-nonmm-unstable tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
kernel/kexec_core.c: In function 'kernel_kexec':
kernel/kexec_core.c:1138:2: error: label 'Resume_console' defined but not used [-Werror=unused-label]
1138 | Resume_console:
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
fbb5aa47e7b0 ("kexec_core: fix error code path in the KEXEC_JUMP flow")
I have applied the following fix patch.
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Fri, 11 Jul 2025 10:35:39 +1000
Subject: [PATCH] fix up for "kexec_core: fix error code path in the KEXEC_JUMP flow"
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
kernel/kexec_core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
index 842611c0b51a..351cd7d76dfa 100644
--- a/kernel/kexec_core.c
+++ b/kernel/kexec_core.c
@@ -1135,7 +1135,6 @@ int kernel_kexec(void)
dpm_resume_start(PMSG_RESTORE);
Resume_devices:
dpm_resume_end(PMSG_RESTORE);
- Resume_console:
console_resume_all();
thaw_processes();
Restore_console:
--
2.50.0
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-11 0:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 0:58 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-01 1:17 linux-next: build failure after merge of the mm-nonmm-unstable tree Stephen Rothwell
2025-10-17 13:25 Mark Brown
2025-10-17 21:34 ` Andrew Morton
2025-11-16 22:36 Stephen Rothwell
2025-11-16 23:23 Stephen Rothwell
2025-11-19 23:14 ` Stephen Rothwell
2025-11-19 23:48 ` Andrew Morton
2025-11-20 8:55 ` Miguel Ojeda
2025-11-20 10:01 ` Alice Ryhl
2025-12-18 4:30 Stephen Rothwell
2025-12-21 2:58 ` Finn Thain
2025-12-26 16:45 ` Sasha Levin
2025-12-29 8:56 ` Finn Thain
2026-01-01 9:21 ` Finn Thain
2026-01-01 17:01 ` Randy Dunlap
2026-01-01 23:15 ` Finn Thain
2026-01-02 7:29 ` Ard Biesheuvel
2026-01-02 22:09 ` Finn Thain
2026-02-16 13:58 Mark Brown
2026-03-17 14:32 Mark Brown
2026-03-17 15:06 ` Mathieu Desnoyers
2026-03-17 15:07 ` David CARLIER
2026-04-29 9:10 Thierry Reding
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=20250711105804.3447e832@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rafael.j.wysocki@intel$(echo .)com \
/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