Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Markus Probst" <markus.probst@posteo.de>
Cc: linux-leds@vger.kernel.org, lee@kernel.org, gary@garyguo.net,
	linux-pci@vger.kernel.org, ojeda@kernel.org
Subject: Re: [PATCH v25 2/4] rust: leds: add Mode trait
Date: Sun, 13 Sep 2026 16:21:57 +0000	[thread overview]
Message-ID: <20260913162158.14FB71F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260913-rust_leds-v25-2-1a10371d78c3@posteo.de>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The `core` import uses horizontal formatting instead of the required vertical format.
- [Low] The commit message description is not capitalized, violating the LED subsystem guidelines.
--

commit fc494e48581e40fa3f62db639a08746b74e239f2
Author: Markus Probst <markus.probst@posteo.de>

rust: leds: add Mode trait

This commit adds the Mode trait to allow for other types of led class
devices in LedOps.

> rust: leds: add Mode trait

[Severity: Low]
This isn't a bug, but the commit message description is not capitalized,
violating the LED subsystem guidelines.

The global review guidelines for the LED subsystem mandate that the
description following the commit message prefix must be capitalized.

Should the description start with a capital letter, as in "rust: leds: Add
Mode trait"?

[ ... ]

> diff --git a/rust/kernel/led.rs b/rust/kernel/led.rs
> index deda8cc548a8c..7cd8f0504649a 100644
> --- a/rust/kernel/led.rs
> +++ b/rust/kernel/led.rs
> @@ -4,11 +4,7 @@
>  //!
>  //! C header: [`include/linux/leds.h`](srctree/include/linux/leds.h)
>  
> -use core::{
> -    marker::PhantomData,
> -    mem::transmute,
> -    ptr::NonNull, //
> -};
> +use core::{marker::PhantomData, mem::transmute, ops::Deref, ptr::NonNull};

[Severity: Low]
This isn't a bug, but does this import for the core crate use horizontal
formatting instead of the required vertical format?

The kernel Rust coding guidelines explicitly require using the vertical
import style for non-vendored crates. The commit replaces a multi-line
vertical import block with a single-line horizontal block.

Should this be changed back to the vertical format?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260913-rust_leds-v25-0-1a10371d78c3@posteo.de?part=2

  reply	other threads:[~2026-09-13 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 16:15 [PATCH v25 0/4] rust: leds: add led classdev abstractions Markus Probst
2026-09-13 16:15 ` [PATCH v25 1/4] rust: leds: add basic " Markus Probst
2026-09-13 16:28   ` sashiko-bot
2026-09-13 16:15 ` [PATCH v25 2/4] rust: leds: add Mode trait Markus Probst
2026-09-13 16:21   ` sashiko-bot [this message]
2026-09-13 16:24   ` Markus Probst
2026-09-13 16:15 ` [PATCH v25 3/4] rust: leds: add multicolor classdev abstractions Markus Probst
2026-09-13 16:31   ` sashiko-bot
2026-09-13 16:15 ` [PATCH v25 4/4] MAINTAINERS: rust: leds: Add rust abstraction entry Markus Probst

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=20260913162158.14FB71F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=gary@garyguo.net \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox