From: "Danilo Krummrich" <dakr@kernel.org>
To: "Gary Guo" <gary@garyguo.net>
Cc: "Markus Probst" <markus.probst@posteo.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>, "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
rust-for-linux@vger.kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH] rust: ACPI: fix missing match data for PRP0001
Date: Sat, 04 Apr 2026 23:32:44 +0200 [thread overview]
Message-ID: <DHKOXDNO7MBC.PZK5N30ELOCG@kernel.org> (raw)
In-Reply-To: <DHKOQBER5U5N.IHLHH5ORAZCQ@garyguo.net>
On Sat Apr 4, 2026 at 11:23 PM CEST, Gary Guo wrote:
> BTW, if most drivers use driver_data of ID as pointers, why is it defined as
> kernel_ulong_t instead of just `void*`?
I think that's because the ID tables are exported to userspace via
scripts/mod/file2alias.c. If it would be void *, then there could be a mismatch
in size when cross compiling.
next prev parent reply other threads:[~2026-04-04 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 14:06 [PATCH] rust: ACPI: fix missing match data for PRP0001 Markus Probst
2026-04-01 18:32 ` Greg Kroah-Hartman
2026-04-01 18:46 ` Markus Probst
2026-04-01 22:15 ` Danilo Krummrich
2026-04-02 12:31 ` Greg Kroah-Hartman
2026-04-04 21:23 ` Gary Guo
2026-04-04 21:32 ` Danilo Krummrich [this message]
2026-04-05 5:47 ` Greg Kroah-Hartman
2026-04-04 21:33 ` Markus Probst
2026-04-04 21:38 ` Danilo Krummrich
2026-04-04 22:08 ` Gary Guo
2026-04-04 22:07 ` Danilo Krummrich
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=DHKOXDNO7MBC.PZK5N30ELOCG@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox