All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Guru Das Srinagesh" <linux@gurudas.dev>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
	dri-devel@lists.freedesktop.org,
	"Alexandre Courbot" <acourbot@nvidia.com>
Subject: Re: [PATCH] drm: nova-drm: use vertical import style
Date: Mon, 06 Jul 2026 03:24:26 +0000	[thread overview]
Message-ID: <20260706032426.78F861F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260705-drm-vert-imp-v1-1-c7b24e290763@gurudas.dev>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incomplete vertical import conversion and unmerged import paths.
--

commit 4005a285946c405f71ba0fa91578531ee7637244
Author: Guru Das Srinagesh <linux@gurudas.dev>

drm: nova-drm: use vertical import style

This commit converts the module imports to a vertical layout to improve
readability and maintainability.

> diff --git a/drivers/gpu/drm/nova/file.rs b/drivers/gpu/drm/nova/file.rs
> index a3b7bd36792c1..547da5caa58db 100644
> --- a/drivers/gpu/drm/nova/file.rs
> +++ b/drivers/gpu/drm/nova/file.rs
> @@ -1,10 +1,16 @@
>  // SPDX-License-Identifier: GPL-2.0
>  
> -use crate::driver::{NovaDevice, NovaDriver};
> +use crate::driver::{
> +    NovaDevice,
> +    NovaDriver, //
> +};
>  use crate::gem::NovaObject;
>  use kernel::{
>      alloc::flags::*,
> -    drm::{self, gem::BaseObject},
> +    drm::{
> +        self,
> +        gem::BaseObject, //
> +    },
>      pci,
>      prelude::*,
>      uapi,
>  };

[Severity: Low]
This isn't a bug, but does the kernel::{...} block need a trailing //
after uapi, to ensure rustfmt preserves the vertical formatting?

> diff --git a/drivers/gpu/drm/nova/gem.rs b/drivers/gpu/drm/nova/gem.rs
> index 9d8ff7de2c0f7..8d89804257371 100644
> --- a/drivers/gpu/drm/nova/gem.rs
> +++ b/drivers/gpu/drm/nova/gem.rs
> @@ -2,14 +2,21 @@
>  
>  use kernel::{
>      drm,
> -    drm::{gem, gem::BaseObject, DeviceContext},
> +    drm::{
> +        gem,
> +        gem::BaseObject,
> +        DeviceContext, //
> +    },

[Severity: Low]
Could these drm and gem imports be merged? For instance, they might be
combined into a single drm::{self, gem::{self, BaseObject}, DeviceContext, //}
block to avoid redundant paths.

>      page,
>      prelude::*,
>      sync::aref::ARef,
>  };

[Severity: Low]
Similar to the file.rs changes, does this outermost block need a trailing //
after sync::aref::ARef, to maintain the vertical style when formatted?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260705-drm-vert-imp-v1-1-c7b24e290763@gurudas.dev?part=1

      reply	other threads:[~2026-07-06  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  3:18 [PATCH] drm: nova-drm: use vertical import style Guru Das Srinagesh
2026-07-06  3:24 ` sashiko-bot [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=20260706032426.78F861F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux@gurudas.dev \
    --cc=sashiko-reviews@lists.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.