From: Guru Das Srinagesh <linux@gurudas.dev>
To: Link Mauve <linkmauve@linkmauve.fr>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Andreas Hindborg" <a.hindborg@kernel.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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
driver-core@lists.linux.dev, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: rust_dma: use vertical import style
Date: Tue, 21 Jul 2026 00:56:50 -0700 [thread overview]
Message-ID: <al8mQuk8f9l9VgR9@gurudas.dev> (raw)
In-Reply-To: <ak3-PbQ-PdeEWVo4@luna>
On Wed, Jul 08, 2026 at 09:37:33AM +0200, Link Mauve wrote:
> Hi,
>
> On Sun, Jul 05, 2026 at 06:25:37PM -0700, Guru Das Srinagesh wrote:
> > Convert `use` imports to vertical layout for better readability and
> > maintainability.
> >
> > Signed-off-by: Guru Das Srinagesh <linux@gurudas.dev>
> > ---
> > Came across a recent commit bc58905eb07 ("samples: rust_misc_device: use
> > vertical import style") and found a few more locations that could
> > benefit from this cleanup. No functional changes.
> >
> > Separating out patches per-subsystem as per the review feedback in [0].
> >
> > Tested via:
> >
> > $ make LLVM=1 rustfmtcheck || echo "fail"
> > $
> >
> > [0]: https://lore.kernel.org/lkml/20260628-b4-rust-vertical-imports-v1-0-98bc71d4810b@gurudas.dev/
> > ---
> > samples/rust/rust_dma.rs | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/samples/rust/rust_dma.rs b/samples/rust/rust_dma.rs
> > index 5046b4628d0e..c46af109f4aa 100644
> > --- a/samples/rust/rust_dma.rs
> > +++ b/samples/rust/rust_dma.rs
> > @@ -12,9 +12,13 @@
> > Device,
> > DmaMask, //
> > },
> > - page, pci,
> > + page,
> > + pci, //
>
> Usually we put the empty comment at the very end of the imports, not in
> the middle.
>
> > prelude::*,
> > - scatterlist::{Owned, SGTable},
> > + scatterlist::{
> > + Owned,
> > + SGTable, //
> > + },
> > sync::aref::ARef,
>
> So here: ↑
>
> > };
Done. Thank you very much for the review and suggestion.
prev parent reply other threads:[~2026-07-21 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 1:25 [PATCH] samples: rust_dma: use vertical import style Guru Das Srinagesh
2026-07-08 7:37 ` Link Mauve
2026-07-21 7:56 ` Guru Das Srinagesh [this message]
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=al8mQuk8f9l9VgR9@gurudas.dev \
--to=linux@gurudas.dev \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=driver-core@lists.linux.dev \
--cc=gary@garyguo.net \
--cc=linkmauve@linkmauve.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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