mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: 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,
	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.6 0000/1651] 6.6.160-rc2 review
Date: Wed, 21 Oct 2026 09:45:16 +0200	[thread overview]
Message-ID: <2026102152-yield-ripping-7709@gregkh> (raw)
In-Reply-To: <beac545f-9a17-4a47-a4cd-7a705302a35c@gmail.com>

On Tue, Oct 20, 2026 at 09:14:08AM -0700, Florian Fainelli wrote:
> On 10/20/26 00:57, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.160 release.
> > There are 1651 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Thu, 22 Oct 2026 07:53:04 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.160-rc2.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> perf build issues are fixed, however we now we get the MIPS kernel to fail
> building with:
> 
> arch/mips/kernel/ftrace.c: In function 'ftrace_dyn_arch_init_insns':
> arch/mips/kernel/ftrace.c:62:6: error: implicit declaration of function
> 'uasm_in_compat_space_p'; did you mean 'uasm_i_dsra_safe'?
> [-Werror=implicit-function-declaration]
>   if (uasm_in_compat_space_p(MCOUNT_ADDR)) {
>       ^~~~~~~~~~~~~~~~~~~~~~
>       uasm_i_dsra_safe
> cc1: some warnings being treated as errors

Looks like this is missing commit e9f98feb1720 ("mips: unhide
uasm_in_compat_space_p() declaration"), so I'll go queue that up now,

thanks.

greg k-h

  reply	other threads:[~2026-10-21  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20  7:57 Greg Kroah-Hartman
2026-10-20  8:47 ` Brett A C Sheffield
2026-10-20 10:45 ` Pavel Machek
2026-10-20 11:56 ` Miguel Ojeda
2026-10-20 14:56 ` SJ Park
2026-10-20 16:14 ` Florian Fainelli
2026-10-21  7:45   ` Greg Kroah-Hartman [this message]
2026-10-20 18:08 ` Peter Schneider
2026-10-21  3:05 ` Iaroslav Voitovych

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=2026102152-yield-ripping-7709@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --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=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®