From: Helge Deller <deller@gmx.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-parisc <linux-parisc@vger.kernel.org>
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@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, "Vishal Bhoj" <vishal.bhoj@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Daniel Díaz" <daniel.diaz@linaro.org>
Subject: Re: [PATCH 5.15 00/15] 5.15.120-rc1 review
Date: Tue, 4 Jul 2023 09:16:36 +0200 [thread overview]
Message-ID: <d25d0195-b40e-2a03-de75-1bdc1aaf404c@gmx.de> (raw)
In-Reply-To: <CA+G9fYueycAbx7DDR3S57d43UX49SOGnW6igQUZ0voEcapxdYw@mail.gmail.com>
On 7/4/23 09:00, Naresh Kamboju wrote:
> On Tue, 4 Jul 2023 at 00:27, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 5.15.120 release.
>> There are 15 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, 05 Jul 2023 18:45:08 +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/v5.x/stable-review/patch-5.15.120-rc1.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> Following build regressions noticed on stable-rc 5.15.
> This build failure started happening from v5.15.119 from date June 28, 2023.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on parisc:
>
> - build/gcc-11-allnoconfig
> - build/gcc-11-defconfig
> - build/gcc-11-tinyconfig
>
> Build errors:
> =============
> arch/parisc/include/asm/assembly.h: Assembler messages:
> arch/parisc/include/asm/assembly.h:75: Error: symbol `sp' is already defined
> arch/parisc/include/asm/assembly.h:77: Error: symbol `ipsw' is already defined
> make[3]: *** [scripts/Makefile.build:391: arch/parisc/kernel/head.o] Error 1
> arch/parisc/include/asm/assembly.h: Assembler messages:
Greg, could you please pull in the following upstream commit?
It was backported to kernels > 6.0, but with newer binutils it's probably
needed for kernels < 6.0 as well:
commit b5b2a02bcaac7c287694aa0db4837a07bf178626
Author: Ben Hutchings <benh@debian.org>
Date: Thu Jun 15 00:00:02 2023 +0200
parisc: Delete redundant register definitions in <asm/assembly.h>
We define sp and ipsw in <asm/asmregs.h> using ".reg", and when using
current binutils (snapshot 2.40.50.20230611) the definitions in
<asm/assembly.h> using "=" conflict with those:
arch/parisc/include/asm/assembly.h: Assembler messages:
arch/parisc/include/asm/assembly.h:93: Error: symbol `sp' is already defined
arch/parisc/include/asm/assembly.h:95: Error: symbol `ipsw' is already defined
Delete the duplicate definitions in <asm/assembly.h>.
Also delete the definition of gp, which isn't used anywhere.
Signed-off-by: Ben Hutchings <benh@debian.org>
Cc: stable@vger.kernel.org # v6.0+
Signed-off-by: Helge Deller <deller@gmx.de>
Thanks,
Helge
next prev parent reply other threads:[~2023-07-04 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 18:54 Greg Kroah-Hartman
2023-07-04 7:00 ` Naresh Kamboju
2023-07-04 7:16 ` Helge Deller [this message]
2023-07-04 7:31 ` Greg Kroah-Hartman
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=d25d0195-b40e-2a03-de75-1bdc1aaf404c@gmx.de \
--to=deller@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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 \
--cc=vishal.bhoj@linaro.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®