From: "Danilo Krummrich" <dakr@kernel.org>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: <ojeda@kernel.org>, <alex.gaynor@gmail.com>,
<boqun.feng@gmail.com>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <aliceryhl@google.com>,
<tmgross@umich.edu>, <linux-usb@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>,
"Thorsten Leemhuis" <linux@leemhuis.info>
Subject: Re: [PATCH] rust: usb: fix broken call to T::disconnect()
Date: Tue, 04 Nov 2025 00:28:16 +0100 [thread overview]
Message-ID: <DDZG710VN30W.1VGG8JWIELQYV@kernel.org> (raw)
In-Reply-To: <2025110425-anew-squall-2ac8@gregkh>
On Mon Nov 3, 2025 at 11:56 PM CET, Greg KH wrote:
> On Mon, Nov 03, 2025 at 12:01:03PM +0100, Danilo Krummrich wrote:
>> A refactoring of Device::drvdata_obtain() broke T::disconnect() in the
>> USB abstractions.
>>
>> """
>> error[E0599]: no method named `data` found for struct `core::pin::Pin<kbox::Box<T, Kmalloc>>` in the current scope
>> --> rust/kernel/usb.rs:92:34
>> |
>> 92 | T::disconnect(intf, data.data());
>> | ^^^^ method not found in `core::pin::Pin<kbox::Box<T, Kmalloc>>`
>>
>> error: aborting due to 1 previous error
>>
>> For more information about this error, try `rustc --explain E0599`.
>> make[2]: *** [rust/Makefile:553: rust/kernel.o] Error 1
>> make[1]: *** [/builddir/build/BUILD/kernel-6.18.0-build/kernel-next-20251103/linux-6.18.0-0.0.next.20251103.436.vanilla.fc44.x86_64/Makefile:1316: prepare] Error 2
>> make: *** [Makefile:256: __sub-make] Error 2
>> """
>>
>> This slipped through, since the USB abstractions are globally disabled.
>> However, the USB tree recently enabled them, hence it showed up in
>> linux-next.
>
> Sorry about this, should we also enable it in the driver-core-next tree
> as well, to catch these types of things?
No worries -- I actually enabled it locally, but then forgot to re-test after a
rebase.
I'm fine either way, I only expect one more patch touching the USB stuff in this
cycle.
next prev parent reply other threads:[~2025-11-03 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 11:01 [PATCH] rust: usb: fix broken call to T::disconnect() Danilo Krummrich
2025-11-03 11:24 ` Alice Ryhl
2025-11-03 12:43 ` Thorsten Leemhuis
2025-11-03 22:56 ` Greg KH
2025-11-03 23:28 ` Danilo Krummrich [this message]
2025-11-03 23:37 ` Danilo Krummrich
2025-11-03 23:37 ` Daniel Almeida
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=DDZG710VN30W.1VGG8JWIELQYV@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.