Rust for Linux List
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Alvin Sun <alvin.sun@linux.dev>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"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>,
	"Danilo Krummrich" <dakr@kernel.org>,
	rust-for-linux@vger.kernel.org, linux-block@vger.kernel.org,
	"Onur Özkan" <work@onurozkan.dev>
Subject: Re: [PATCH v2 3/5] rust: miscdevice: remove redundant imports
Date: Wed, 20 May 2026 05:59:01 +0300	[thread overview]
Message-ID: <20260520025902.34629-1-work@onurozkan.dev> (raw)
In-Reply-To: <20260520-miscdev-use-format-v2-3-64dc48fc1345@linux.dev>

On Wed, 20 May 2026 10:40:10 +0800
Alvin Sun <alvin.sun@linux.dev> wrote:

> Drop `Error`, `Result`, `Pin`, `c_int`, `c_long`, `c_uint`, and
> `c_ulong` imports already provided by `kernel::prelude`.
> 
> Signed-off-by: Alvin Sun <alvin.sun@linux.dev>

Reviewed-by: Onur Özkan <work@onurozkan.dev>

> ---
>  rust/kernel/miscdevice.rs | 13 +------------
>  1 file changed, 1 insertion(+), 12 deletions(-)
> 
> diff --git a/rust/kernel/miscdevice.rs b/rust/kernel/miscdevice.rs
> index 05a6b6b9770f2..83ce50def5ac9 100644
> --- a/rust/kernel/miscdevice.rs
> +++ b/rust/kernel/miscdevice.rs
> @@ -13,16 +13,8 @@
>      device::Device,
>      error::{
>          to_result,
> -        Error,
> -        Result,
>          VTABLE_DEFAULT_ERROR, //
>      },
> -    ffi::{
> -        c_int,
> -        c_long,
> -        c_uint,
> -        c_ulong, //
> -    },
>      fs::{
>          File,
>          Kiocb, //
> @@ -39,10 +31,7 @@
>          Opaque, //
>      },
>  };
> -use core::{
> -    marker::PhantomData,
> -    pin::Pin, //
> -};
> +use core::marker::PhantomData;
>  
>  /// Options for creating a misc device.
>  #[derive(Copy, Clone)]
> 
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2026-05-20  2:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  2:40 [PATCH v2 0/5] rust: use vertical import style and remove redundant imports Alvin Sun
2026-05-20  2:40 ` [PATCH v2 1/5] rust: miscdevice: use vertical import style Alvin Sun
2026-05-20  2:57   ` Onur Özkan
2026-05-20  2:40 ` [PATCH v2 2/5] samples: rust_misc_device: " Alvin Sun
2026-05-20  2:58   ` Onur Özkan
2026-05-20  2:40 ` [PATCH v2 3/5] rust: miscdevice: remove redundant imports Alvin Sun
2026-05-20  2:59   ` Onur Özkan [this message]
2026-05-20  2:40 ` [PATCH v2 4/5] rust: block: mq: use vertical import style Alvin Sun
2026-05-20  2:59   ` Onur Özkan
2026-05-20  2:40 ` [PATCH v2 5/5] rust: block: mq: remove redundant imports and format Alvin Sun
2026-05-20  2:59   ` Onur Özkan

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=20260520025902.34629-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=alvin.sun@linux.dev \
    --cc=arnd@arndb.de \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@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