From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.1 000/225] 6.1.33-rc1 review
Date: Thu, 8 Jun 2023 19:57:02 +0200 [thread overview]
Message-ID: <2023060848-vice-dismay-a6f2@gregkh> (raw)
In-Reply-To: <cf6f959e-2885-1e7b-826d-61bff351ff14@roeck-us.net>
On Thu, Jun 08, 2023 at 08:08:50AM -0700, Guenter Roeck wrote:
> On 6/7/23 13:13, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.33 release.
> > There are 225 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 Fri, 09 Jun 2023 20:07:31 +0000.
> > Anything received after that time might be too late.
> >
>
> Failed builds:
> loongarch:defconfig
> loongarch:allnoconfig
> loongarch:tinyconfig
> loongarch:allmodconfig
>
> arch/loongarch/kernel/traps.c: In function 'trap_init':
> arch/loongarch/kernel/traps.c:815:21: error: 'EXCCODE_BCE' undeclared
>
> EXCCODE_BCE is indeed undeclared in v6.1.y.
>
> Commit 'LoongArch: Relay BCE exceptions to userland as SIGSEGV with si_code=SEGV_BNDERR'
> is not marked Fixes: or stable: and should arguably not have been backported.
>
> The same problem affects 6.3.
Thanks, I'll go drop this from both trees and push out -rc2 releases.
greg k-h
prev parent reply other threads:[~2023-06-08 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 20:13 Greg Kroah-Hartman
2023-06-07 20:16 ` [PATCH 6.1 205/225] test_firmware: fix the memory leak of the allocated firmware buffer Greg Kroah-Hartman
2023-06-08 1:22 ` [PATCH 6.1 000/225] 6.1.33-rc1 review Shuah Khan
2023-06-08 3:21 ` Florian Fainelli
2023-06-08 6:38 ` Markus Reichelt
2023-06-08 7:24 ` Chris Paterson
2023-06-08 9:43 ` Conor Dooley
2023-06-08 11:07 ` Naresh Kamboju
2023-06-08 11:19 ` ogasawara takeshi
2023-06-08 11:30 ` Bagas Sanjaya
2023-06-08 15:08 ` Guenter Roeck
2023-06-08 17:57 ` Greg Kroah-Hartman [this message]
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=2023060848-vice-dismay-a6f2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.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@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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®