From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@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, slade@sladewatkins.com
Subject: Re: [PATCH 5.15 000/277] 5.15.34-rc2 review
Date: Wed, 13 Apr 2022 07:48:37 -0700 [thread overview]
Message-ID: <20220413144837.GA2401071@roeck-us.net> (raw)
In-Reply-To: <20220412173836.126811734@linuxfoundation.org>
On Tue, Apr 12, 2022 at 07:47:07PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.34 release.
> There are 277 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, 14 Apr 2022 17:37:56 +0000.
> Anything received after that time might be too late.
Build results:
total: 156 pass: 155 fail: 1
Failed builds:
nds32:allmodconfig
Qemu test results:
total: 488 pass: 488 fail: 0
Building nds32:allmodconfig ... failed
--------------
Error log:
net/core/lwtunnel.o: in function `lwtunnel_fill_encap':
(.text+0x4d6): relocation truncated to fit: R_NDS32_9_PCREL_RELA against `.text'
I have no idea what causes the problem. Given that nds32 has been removed
from mainline, we should probably not bother. I may stop test building it
if the problem is persistent over multiple stable releases.
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2022-04-13 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 17:47 [PATCH 5.15 000/277] 5.15.34-rc2 review Greg Kroah-Hartman
2022-04-12 22:21 ` Shuah Khan
2022-04-13 2:02 ` Fox Chen
2022-04-13 6:10 ` Naresh Kamboju
2022-04-13 8:59 ` Ron Economos
2022-04-13 14:48 ` Guenter Roeck [this message]
2022-04-13 19:18 ` Florian Fainelli
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=20220413144837.GA2401071@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@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