From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Peter Schneider <pschneider1968@googlemail.com>,
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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 00/64] 6.1.127-rc1 review
Date: Wed, 22 Jan 2025 08:38:43 +0100 [thread overview]
Message-ID: <2025012221-whenever-sterile-11e2@gregkh> (raw)
In-Reply-To: <2025012244-rigor-boat-b44d@gregkh>
On Wed, Jan 22, 2025 at 08:35:11AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 21, 2025 at 10:57:09PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > On Tue, Jan 21, 2025 at 08:32:01PM +0100, Peter Schneider wrote:
> > > Am 21.01.2025 um 18:51 schrieb Greg Kroah-Hartman:
> > > > This is the start of the stable review cycle for the 6.1.127 release.
> > > > There are 64 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.
> > >
> > >
> > > On my 2-socket Ivy Bridge Xeon E5-2697 v2 server, I get a build error:
> > >
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn303.o
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn31.o
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn314.o
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn315.o
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn316.o
> > > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_dcn32.o
> > > LD [M] drivers/gpu/drm/amd/amdgpu/amdgpu.o
> > > AR drivers/gpu/built-in.a
> > > AR drivers/built-in.a
> > > AR built-in.a
> > > AR vmlinux.a
> > > LD vmlinux.o
> > > OBJCOPY modules.builtin.modinfo
> > > GEN modules.builtin
> > > GEN .vmlinux.objs
> > > MODPOST Module.symvers
> > > ERROR: modpost: module inv-icm42600-spi uses symbol
> > > inv_icm42600_spi_regmap_config from namespace IIO_ICM42600, but does not
> > > import it.
> > > make[1]: *** [scripts/Makefile.modpost:127: Module.symvers] Fehler 1
> > > make: *** [Makefile:1961: modpost] Fehler 2
> > > root@linus:/usr/src/linux-stable-rc#
> > >
> > > I have attached my .config file.
> >
> > Reverting c0f866de4ce447bca3191b9cefac60c4b36a7922 would solve the
> > problem, but then maybe the other icm42600 related commits are
> > incorrect? Guess it's a missing prequisite for that commit missing in
> > 6.1.y.
> >
> > Can confirm the failure as well in a test build for Debian.
>
> Ok, let me go fix this up, it's due to the namespace symbol stuff not
> being in 6.1.y, I'll hand edit the offending commit and push out a -rc2.
Same issue should be present in the 5.15-rc release, I'll go fix it up
there too. Odd it didn't get caught in my build testing...
greg k-h
next prev parent reply other threads:[~2025-01-22 7:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 17:51 [PATCH 6.1 00/64] 6.1.127-rc1 review Greg Kroah-Hartman
2025-01-21 17:52 ` [PATCH 6.1 22/64] kheaders: Ignore silly-rename files Greg Kroah-Hartman
2025-01-21 18:44 ` [PATCH 6.1 00/64] 6.1.127-rc1 review Florian Fainelli
2025-01-21 19:32 ` Peter Schneider
2025-01-21 21:57 ` Salvatore Bonaccorso
2025-01-22 7:35 ` Greg Kroah-Hartman
2025-01-22 7:38 ` Greg Kroah-Hartman [this message]
2025-01-22 5:32 ` Ron Economos
2025-01-21 23:35 ` Shuah Khan
2025-01-21 23:46 ` SeongJae Park
2025-01-22 20:17 ` [PATCH 6.1] " Hardik Garg
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=2025012221-whenever-sterile-11e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=carnil@debian.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.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=pschneider1968@googlemail.com \
--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