[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250729102953.141412-1-abhinav.ogl@gmail.com>
Date: Tue, 29 Jul 2025 15:59:53 +0530
From: herculoxz <abhinav.ogl@...il.com>
To: linux-pci@...r.kernel.org
Cc: rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org,
dakr@...nel.org,
bhelgaas@...gle.com,
kwilczynski@...nel.org,
ojeda@...nel.org,
alex.gaynor@...il.com,
boqun.feng@...il.com,
gary@...yguo.net,
bjorn3_gh@...tonmail.com,
lossin@...nel.org,
a.hindborg@...nel.org,
aliceryhl@...gle.com,
tmgross@...ch.edu,
Abhinav Ananthu <abhinav.ogl@...il.com>
Subject: [PATCH v2] rust: pci: Use explicit types in FFI callbacks
From: Abhinav Ananthu <abhinav.ogl@...il.com>
Update PCI FFI callback signatures to use `c_int` from the prelude,
instead of accessing it via `kernel::ffi::c_int`.
This follows Rust-for-Linux coding guidelines and improves ABI
correctness when interfacing with C code.
Signed-off-by: Abhinav Ananthu <abhinav.ogl@...il.com>
---
rust/kernel/pci.rs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
index 5ce07999168e..fbeeaec4e044 100644
--- a/rust/kernel/pci.rs
+++ b/rust/kernel/pci.rs
@@ -61,7 +61,7 @@ impl<T: Driver + 'static> Adapter<T> {
extern "C" fn probe_callback(
pdev: *mut bindings::pci_dev,
id: *const bindings::pci_device_id,
- ) -> kernel::ffi::c_int {
+ ) -> c_int {
// SAFETY: The PCI bus only ever calls the probe callback with a valid pointer to a
// `struct pci_dev`.
//
@@ -333,7 +333,7 @@ unsafe fn do_release(pdev: &Device, ioptr: usize, num: i32) {
// `ioptr` is valid by the safety requirements.
// `num` is valid by the safety requirements.
unsafe {
- bindings::pci_iounmap(pdev.as_raw(), ioptr as *mut kernel::ffi::c_void);
+ bindings::pci_iounmap(pdev.as_raw(), ioptr as *mut c_void);
bindings::pci_release_region(pdev.as_raw(), num);
}
}
--
2.34.1
Powered by blists - more mailing lists