From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.6.70
Date: Fri, 10 Jan 2025 13:43:17 +0100 [thread overview]
Message-ID: <2025011058-mortify-decimal-96f6@gregkh> (raw)
In-Reply-To: <10c7be00-b1f8-4389-801b-fb2d0b22468d@googlemail.com>
On Fri, Jan 10, 2025 at 08:51:33AM +0000, Chris Clayton wrote:
> On 09/01/2025 12:56, Greg Kroah-Hartman wrote:
> > I'm announcing the release of the 6.6.70 kernel.
> >
> > All users of the 6.6 kernel series must upgrade.
> >
> > The updated 6.6.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.6.y
> > and can be browsed at the normal kernel.org git web browser:
> > https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------
> The build of stable 6.6.70 is failing on my config.
>
> The error messages are:
> ld.bfd: kernel/kexec_core.o: in function `__crash_kexec':
> kexec_core.c:(.text+0x257): undefined reference to `machine_crash_shutdown'
> ld.bfd: kernel/kexec.o: in function `do_kexec_load':
> kexec.c:(.text+0x13e): undefined reference to `arch_kexec_protect_crashkres'
> ld.bfd: kexec.c:(.text+0x178): undefined reference to `arch_kexec_unprotect_crashkres'
>
> My config file for building 6.6.x kernels is attached.
>
> Happy to test a fix but please CC me because I'm not subscribed to LKML.
I think I have this fixed up now and will do a new release in a few
minutes with just this resolved.
thanks!
greg k-h
next prev parent reply other threads:[~2025-01-10 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 12:56 Linux 6.6.70 Greg Kroah-Hartman
2025-01-09 12:56 ` Greg Kroah-Hartman
2025-01-10 8:51 ` Chris Clayton
2025-01-10 12:43 ` Greg Kroah-Hartman [this message]
2025-01-10 13:51 ` Greg Kroah-Hartman
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=2025011058-mortify-decimal-96f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=chris2553@googlemail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@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 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.