mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Julien Thierry <jthierry@redhat.com>,
	James Morse <james.morse@arm.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 5.10 000/355] 5.10.239-rc1 review
Date: Tue, 24 Jun 2025 12:41:08 +0200	[thread overview]
Message-ID: <aFqAxKT6C7idQY32@duo.ucw.cz> (raw)
In-Reply-To: <CA+G9fYt2e-ZGhU57oqWwC1_t2RPgxLCJFVC0Pa8-fYPkZcUvVQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3765 bytes --]

Hi!

> > This is the start of the stable review cycle for the 5.10.239 release.
> > There are 355 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, 25 Jun 2025 13:05:51 +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.10.239-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.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> Regressions on arm64 tinyconfig builds with gcc-12 and clang failed on
> the Linux stable-rc 5.10.239-rc1.

Yeah, we see same problems:


814
  CC      arch/arm64/kernel/asm-offsets.s
815
In file included from ./arch/arm64/include/asm/alternative.h:6,
816
                 from ./arch/arm64/include/asm/sysreg.h:1050,
817
                 from ./arch/arm64/include/asm/cputype.h:194,
818
                 from ./arch/arm64/include/asm/cache.h:8,
819
                 from ./include/linux/cache.h:6,
820
                 from ./include/linux/printk.h:9,
821
                 from ./include/linux/kernel.h:17,
822
                 from ./include/linux/list.h:9,
823
                 from ./include/linux/kobject.h:19,
824
                 from ./include/linux/of.h:17,
825
                 from ./include/linux/irqdomain.h:35,
826
                 from ./include/linux/acpi.h:13,
827
                 from ./include/acpi/apei.h:9,
828
                 from ./include/acpi/ghes.h:5,
829
                 from ./include/linux/arm_sdei.h:8,
830
                 from arch/arm64/kernel/asm-offsets.c:10:
831
./arch/arm64/include/asm/insn.h: In function 'aarch64_insn_gen_atomic_ld_op':
832
./arch/arm64/include/asm/insn.h:26:54: error: 'FAULT_BRK_IMM' undeclared (first use in this function)
833
   26 | #define AARCH64_BREAK_FAULT    (AARCH64_BREAK_MON | (FAULT_BRK_IMM << 5))
834
      |                                                      ^~~~~~~~~~~~~
835
./arch/arm64/include/asm/insn.h:573:9: note: in expansion of macro 'AARCH64_BREAK_FAULT'
836
  573 |  return AARCH64_BREAK_FAULT;
837
      |         ^~~~~~~~~~~~~~~~~~~
838
./arch/arm64/include/asm/insn.h:26:54: note: each undeclared identifier is reported only once for each function it appears in
839
   26 | #define AARCH64_BREAK_FAULT    (AARCH64_BREAK_MON | (FAULT_BRK_IMM << 5))
840
      |                                                      ^~~~~~~~~~~~~
841
./arch/arm64/include/asm/insn.h:573:9: note: in expansion of macro 'AARCH64_BREAK_FAULT'
842
  573 |  return AARCH64_BREAK_FAULT;
843
      |         ^~~~~~~~~~~~~~~~~~~
844
./arch/arm64/include/asm/insn.h: In function 'aarch64_insn_gen_cas':
845
./arch/arm64/include/asm/insn.h:26:54: error: 'FAULT_BRK_IMM' undeclared (first use in this function)
846
   26 | #define AARCH64_BREAK_FAULT    (AARCH64_BREAK_MON | (FAULT_BRK_IMM << 5))
847
      |                                                      ^~~~~~~~~~~~~
848
./arch/arm64/include/asm/insn.h:583:9: note: in expansion of macro 'AARCH64_BREAK_FAULT'
849
  583 |  return AARCH64_BREAK_FAULT;
850
      |         ^~~~~~~~~~~~~~~~~~~
851
make[1]: *** [scripts/Makefile.build:117: arch/arm64/kernel/asm-offsets.s] Error 1
852
make: *** [Makefile:1262: prepare0] Error 2

BR,
										Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2025-06-24 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 13:03 Greg Kroah-Hartman
2025-06-23 20:26 ` Naresh Kamboju
2025-06-24 10:27   ` Greg Kroah-Hartman
2025-06-24 10:41   ` Pavel Machek [this message]
2025-06-23 20:30 ` Florian Fainelli
2025-06-24  7:02 ` Dominique Martinet

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=aFqAxKT6C7idQY32@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=james.morse@arm.com \
    --cc=jonathanh@nvidia.com \
    --cc=jthierry@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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=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=will@kernel.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®