From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
pavel@denx.de, sam@ravnborg.org
Subject: Re: [PATCH 6.8 000/710] 6.8.2-rc2 review
Date: Tue, 26 Mar 2024 09:27:36 -0600 [thread overview]
Message-ID: <289f01fa-a323-4021-8a1d-a12b474d055b@linaro.org> (raw)
In-Reply-To: <20240325120018.1768449-1-sashal@kernel.org>
Hello!
On 25/03/24 6:00 a. m., Sasha Levin wrote:
> This is the start of the stable review cycle for the 6.8.2 release.
> There are 710 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 Wed Mar 27 12:00:13 PM UTC 2024.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-6.8.y&id2=v6.8.1
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.8.y
> and the diffstat can be found below.
>
> Thanks,
> Sasha
There is a build regression on SPARC with allmodconfig, with GCC 8 and GCC 11. These are the first error messages:
-----8<-----
/builds/linux/arch/sparc/kernel/traps_64.c:253:6: error: no previous prototype for 'is_no_fault_exception' [-Werror=missing-prototypes]
253 | bool is_no_fault_exception(struct pt_regs *regs)
| ^~~~~~~~~~~~~~~~~~~~~
/builds/linux/arch/sparc/kernel/traps_64.c:2035:6: error: no previous prototype for 'do_mcd_err' [-Werror=missing-prototypes]
2035 | void do_mcd_err(struct pt_regs *regs, struct sun4v_error_entry ent)
| ^~~~~~~~~~
/builds/linux/arch/sparc/kernel/traps_64.c:2153:6: error: no previous prototype for 'sun4v_nonresum_error_user_handled' [-Werror=missing-prototypes]
2153 | bool sun4v_nonresum_error_user_handled(struct pt_regs *regs,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
----->8-----
More information (complete logs, binaries, kernel config, etc.) here:
https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/2eDAKInwlwcpYzt67s8SukhrZEZ
Reproducer:
tuxmake --runtime podman --target-arch sparc --toolchain gcc-11 --kconfig allmodconfig
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
next prev parent reply other threads:[~2024-03-26 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 Sasha Levin
2024-03-25 15:18 ` Daniel Díaz
2024-03-25 23:50 ` Sasha Levin
2024-03-25 17:56 ` SeongJae Park
2024-03-25 18:14 ` Naresh Kamboju
2024-03-25 20:13 ` Justin Forbes
2024-03-25 21:29 ` Florian Fainelli
2024-03-26 3:45 ` Bagas Sanjaya
2024-03-26 9:00 ` Ron Economos
2024-03-26 11:19 ` Jiri Slaby
2024-03-26 15:27 ` Daniel Díaz [this message]
2024-03-26 16:31 ` Shuah Khan
2024-03-26 21:34 ` Shreeya Patel
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=289f01fa-a323-4021-8a1d-a12b474d055b@linaro.org \
--to=daniel.diaz@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sam@ravnborg.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--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 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®