From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christian Heusel <christian@heusel.eu>
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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.15 000/592] 6.15.4-rc1 review
Date: Tue, 24 Jun 2025 11:04:53 +0100 [thread overview]
Message-ID: <2025062442-ablaze-blouse-9327@gregkh> (raw)
In-Reply-To: <a0ebb389-f088-417b-9fd4-ac8c100d206f@heusel.eu>
On Mon, Jun 23, 2025 at 03:50:45PM +0200, Christian Heusel wrote:
> On 25/06/23 02:59PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.15.4 release.
> > There are 592 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:55 +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/v6.x/stable-review/patch-6.15.4-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-6.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Hey Greg,
>
> this stable release candidate does not build for me as-is on x86:
>
> error[E0432]: unresolved import `crate::sync::Completion`
> --> rust/kernel/devres.rs:16:22
> |
> 16 | sync::{rcu, Arc, Completion},
> | ^^^^^^^^^^ no `Completion` in `sync`
>
> error[E0412]: cannot find type `Bound` in this scope
> --> rust/kernel/devres.rs:226:49
> |
> 226 | pub fn access<'a>(&'a self, dev: &'a Device<Bound>) -> Result<&'a T> {
> | ^^^^^ not found in this scope
> |
> help: consider importing this enum
> |
> 8 + use core::range::Bound;
> |
>
> error[E0107]: struct takes 0 generic arguments but 1 generic argument was supplied
> --> rust/kernel/devres.rs:226:42
> |
> 226 | pub fn access<'a>(&'a self, dev: &'a Device<Bound>) -> Result<&'a T> {
> | ^^^^^^------- help: remove the unnecessary generics
> | |
> | expected 0 generic arguments
> |
> note: struct defined here, with 0 generic parameters
> --> rust/kernel/device.rs:45:12
> |
> 45 | pub struct Device(Opaque<bindings::device>);
> | ^^^^^^
>
> error[E0600]: cannot apply unary operator `!` to type `()`
> --> rust/kernel/devres.rs:172:12
> |
> 172 | if !inner.data.revoke() {
> | ^^^^^^^^^^^^^^^^^^^^ cannot apply unary operator `!`
>
> error[E0599]: no method named `access` found for struct `Revocable` in the current scope
> --> rust/kernel/devres.rs:234:33
> |
> 234 | Ok(unsafe { self.0.data.access() })
> | ^^^^^^
> |
> ::: rust/kernel/revocable.rs:64:1
> |
> 64 | #[pin_data(PinnedDrop)]
> | ----------------------- method `access` not found for this struct
> |
> help: there is a method `try_access` with a similar name
> |
> 234 | Ok(unsafe { self.0.data.try_access() })
> | ++++
>
> error[E0599]: no method named `try_access_with` found for struct `Revocable` in the current scope
> --> rust/kernel/devres.rs:244:21
> |
> 244 | self.0.data.try_access_with(f)
> | ^^^^^^^^^^^^^^^
> |
> ::: rust/kernel/revocable.rs:64:1
> |
> 64 | #[pin_data(PinnedDrop)]
> | ----------------------- method `try_access_with` not found for this struct
> |
> help: there is a method `try_access` with a similar name, but with different arguments
> --> rust/kernel/revocable.rs:97:5
> |
> 97 | pub fn try_access(&self) -> Option<RevocableGuard<'_, T>> {
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> error[E0308]: mismatched types
> --> rust/kernel/devres.rs:257:21
> |
> 257 | if unsafe { self.0.data.revoke_nosync() } {
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `bool`, found `()`
>
> error: aborting due to 7 previous errors
>
> Some errors have detailed explanations: E0107, E0308, E0412, E0432, E0599, E0600.
> For more information about an error, try `rustc --explain E0107`.
> make[2]: *** [rust/Makefile:536: rust/kernel.o] Error 1
> make[1]: *** [/build/linux/src/linux-6.15.3/Makefile:1280: prepare] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
Thanks for the report, now fixed.
greg k-h
next prev parent reply other threads:[~2025-06-24 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 12:59 Greg Kroah-Hartman
2025-06-23 13:50 ` Christian Heusel
2025-06-23 23:15 ` Benno Lossin
2025-06-24 10:04 ` Greg Kroah-Hartman [this message]
2025-06-23 15:17 ` Ronald Warsow
2025-06-23 20:11 ` Achill Gilgenast
2025-06-23 20:45 ` Peter Schneider
2025-06-23 20:56 ` Naresh Kamboju
2025-06-23 22:39 ` Florian Fainelli
2025-06-24 8:07 ` Ron Economos
2025-06-24 8:43 ` Luna Jernberg
2025-06-24 11:48 ` Mark Brown
2025-06-24 11:57 ` Takeshi Ogasawara
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=2025062442-ablaze-blouse-9327@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=christian@heusel.eu \
--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=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
all inboxes | Powered by JetHome®