From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Brett A C Sheffield <bacs@librecast.net>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/621] 6.18.57-rc1 review
Date: Wed, 14 Oct 2026 11:01:52 +0200 [thread overview]
Message-ID: <2026101445-announcer-unreached-bd03@gregkh> (raw)
In-Reply-To: <as8_EiojooHC5H-v@karahi.librecast.net>
On Wed, Oct 14, 2026 at 10:36:34AM +0200, Brett A C Sheffield wrote:
> On 2026-10-13 21:27, Sasha Levin wrote:
> > > Build failing on amd64:
> > >
> > > /usr/x86_64-pc-linux-gnu/binutils-bin/2.47/ld: vmlinux.o: in function `gss_krb5_get_mic_v2':
> > > (.text+0xfc2762): undefined reference to `crypto_krb5_get_mic'
> >
> > Thanks for the report. The krb5 patches in the queue need a select of
> > CRYPTO_KRB5 that was missing. Queued for 6.18.
>
> Thanks.
>
> Will there be an RC2?
Yes, let me work on that today...
next prev parent reply other threads:[~2026-10-14 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:29 Greg Kroah-Hartman
2026-10-13 12:29 ` Brett A C Sheffield
2026-10-13 13:13 ` Pavel Machek
2026-10-13 19:19 ` Florian Fainelli
2026-10-13 20:20 ` Peter Schneider
2026-10-14 1:27 ` Sasha Levin
2026-10-14 8:36 ` Brett A C Sheffield
2026-10-14 9:01 ` Greg Kroah-Hartman [this message]
2026-10-13 17:07 ` Miguel Ojeda
2026-10-13 23:11 ` Shuah Khan
2026-10-14 5:43 ` Wentao Guan
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=2026101445-announcer-unreached-bd03@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bacs@librecast.net \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®