public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhi Wang <zhiw@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: <bhelgaas@google.com>, <kwilczynski@kernel.org>,
	<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-pci@vger.kernel.org>,
	<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: pci: use "kernel vertical" style for imports
Date: Thu, 6 Nov 2025 11:44:11 +0200	[thread overview]
Message-ID: <20251106114411.370711ce.zhiw@nvidia.com> (raw)
In-Reply-To: <20251105120352.77603-1-dakr@kernel.org>

On Wed,  5 Nov 2025 13:03:28 +0100
Danilo Krummrich <dakr@kernel.org> wrote:

> Convert all imports in the PCI Rust module to use "kernel vertical"
> style.
> 
> With this subsequent patches neither introduce unrelated changes nor
> leave an inconsistent import pattern.
> 
> While at it, drop unnecessary imports covered by prelude::*.
> 

Looking good to me and test on the driver-core-testing branch.

Reviewed-by: Zhi Wang <zhiw@nvidia.com>

> Link: https://docs.kernel.org/rust/coding-guidelines.html#imports
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
>  rust/kernel/pci.rs     | 35 +++++++++++++++++++++++++++--------
>  rust/kernel/pci/id.rs  |  5 ++++-
>  rust/kernel/pci/io.rs  | 13 ++++++++-----
>  rust/kernel/pci/irq.rs | 14 +++++++++-----
>  4 files changed, 48 insertions(+), 19 deletions(-)
> 
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index b68ef4e575fc..410b79d46632 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -5,27 +5,46 @@
>  //! C header: [`include/linux/pci.h`](srctree/include/linux/pci.h)
>  
>  use crate::{
> -    bindings, container_of, device,
> -    device_id::{RawDeviceId, RawDeviceIdIndex},
> +    bindings,
> +    container_of,
> +    device,
> +    device_id::{
> +        RawDeviceId,
> +        RawDeviceIdIndex, //
> +    },
>      driver,
> -    error::{from_result, to_result, Result},
> +    error::{
> +        from_result,
> +        to_result, //
> +    },
> +    prelude::*,
>      str::CStr,
>      types::Opaque,
> -    ThisModule,
> +    ThisModule, //
>  };
>  use core::{
>      marker::PhantomData,
> -    ptr::{addr_of_mut, NonNull},
> +    ptr::{
> +        addr_of_mut,
> +        NonNull, //
> +    },
>  };
> -use kernel::prelude::*;
>  
>  mod id;
>  mod io;
>  mod irq;
>  
> -pub use self::id::{Class, ClassMask, Vendor};
> +pub use self::id::{
> +    Class,
> +    ClassMask,
> +    Vendor, //
> +};
>  pub use self::io::Bar;
> -pub use self::irq::{IrqType, IrqTypes, IrqVector};
> +pub use self::irq::{
> +    IrqType,
> +    IrqTypes,
> +    IrqVector, //
> +};
>  
>  /// An adapter for the registration of PCI drivers.
>  pub struct Adapter<T: Driver>(T);
> diff --git a/rust/kernel/pci/id.rs b/rust/kernel/pci/id.rs
> index 7f2a7f57507f..a1de70b2176a 100644
> --- a/rust/kernel/pci/id.rs
> +++ b/rust/kernel/pci/id.rs
> @@ -4,7 +4,10 @@
>  //!
>  //! This module contains PCI class codes, Vendor IDs, and supporting
> types. 
> -use crate::{bindings, error::code::EINVAL, error::Error, prelude::*};
> +use crate::{
> +    bindings,
> +    prelude::*, //
> +};
>  use core::fmt;
>  
>  /// PCI device class codes.
> diff --git a/rust/kernel/pci/io.rs b/rust/kernel/pci/io.rs
> index 3684276b326b..0d55c3139b6f 100644
> --- a/rust/kernel/pci/io.rs
> +++ b/rust/kernel/pci/io.rs
> @@ -4,14 +4,17 @@
>  
>  use super::Device;
>  use crate::{
> -    bindings, device,
> +    bindings,
> +    device,
>      devres::Devres,
> -    io::{Io, IoRaw},
> -    str::CStr,
> -    sync::aref::ARef,
> +    io::{
> +        Io,
> +        IoRaw, //
> +    },
> +    prelude::*,
> +    sync::aref::ARef, //
>  };
>  use core::ops::Deref;
> -use kernel::prelude::*;
>  
>  /// A PCI BAR to perform I/O-Operations on.
>  ///
> diff --git a/rust/kernel/pci/irq.rs b/rust/kernel/pci/irq.rs
> index 782a524fe11c..063b6a5101ff 100644
> --- a/rust/kernel/pci/irq.rs
> +++ b/rust/kernel/pci/irq.rs
> @@ -4,16 +4,20 @@
>  
>  use super::Device;
>  use crate::{
> -    bindings, device,
> +    bindings,
> +    device,
>      device::Bound,
>      devres,
> -    error::{to_result, Result},
> -    irq::{self, IrqRequest},
> +    error::to_result,
> +    irq::{
> +        self,
> +        IrqRequest, //
> +    },
> +    prelude::*,
>      str::CStr,
> -    sync::aref::ARef,
> +    sync::aref::ARef, //
>  };
>  use core::ops::RangeInclusive;
> -use kernel::prelude::*;
>  
>  /// IRQ type flags for PCI interrupt allocation.
>  #[derive(Debug, Clone, Copy)]


  reply	other threads:[~2025-11-06  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 12:03 [PATCH] rust: pci: use "kernel vertical" style for imports Danilo Krummrich
2025-11-06  9:44 ` Zhi Wang [this message]
2025-11-11  8:53 ` 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=20251106114411.370711ce.zhiw@nvidia.com \
    --to=zhiw@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox