From: sashiko-bot@kernel.org
To: "Dongdong Hao" <doubled@leap-io-kernel.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v5 2/2] scsi: leapraid: Add driver documentation
Date: Tue, 04 Aug 2026 09:33:30 +0000 [thread overview]
Message-ID: <20260804093331.417E61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <6dc9239844dc00cd053ea0649cc9fe05cad1d98a.1785823793.git.doubled@leap-io-kernel.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The driver introduces a non-standard sysfs attribute `ncq_cmd_prio_enable` for NCQ priority configuration, causing ABI fragmentation.
- [Low] Missing required blank lines after section title underlines in reStructuredText documentation.
--
--- Patch [2]: [PATCH v5 2/2] scsi: leapraid: Add driver documentation ---
commit 630ad4ee0c14f18c620eec6823a389cf9f5654aa
Author: Dongdong Hao <doubled@leap-io-kernel.com>
scsi: leapraid: Add driver documentation
This patch adds the necessary documentation for the LeapRAID SCSI driver
to the kernel's documentation tree.
> diff --git a/Documentation/scsi/leapraid.rst b/Documentation/scsi/leapraid.rst
> new file mode 100644
> index 0000000000000..99930ce2b8d04
> --- /dev/null
> +++ b/Documentation/scsi/leapraid.rst
> @@ -0,0 +1,110 @@
[ ... ]
> +Supported devices
> +=================
> +
> +- LeapHBA-8200C
> +
> +Features
> +========
[Severity: Low]
Are we missing a blank line here?
In reStructuredText, a section title's underline needs to be followed by a
blank line. Failing to provide this blank line causes Sphinx documentation
build warnings.
> +- PCIe Gen4 x8 host interface
> +- Support for SAS and SATA devices
[ ... ]
> +LeapRAID specific disk attributes
> +=================================
> +
> +::
> +
> + /sys/class/scsi_disk/host:bus:target:lun/device/sas_device_handle
> + /sys/class/scsi_disk/host:bus:target:lun/device/ncq_cmd_prio_enable
[Severity: Medium]
Does this driver introduce a non-standard sysfs attribute for NCQ priority
configuration?
Using ncq_cmd_prio_enable instead of the standard sas_ncq_prio_enable or
ncq_prio_enable defined in Documentation/ABI/testing/sysfs-block-device can
break userspace compatibility. When a user attempts to configure NCQ priority
via sysfs using generic scripts or udev rules, it might fail for this driver.
> +
> +The read-only attribute "sas_device_handle" represents the disk's device
> +handle, which is a unique identifier maintained by the firmware.
[ ... ]
> +4. poll_queues
> +--------------
> +
> +This parameter specifies the number of I/O queues to be used when operating
> +in io_uring poll mode. The default value is 0.
> +
> +File Location
> +=============
[Severity: Low]
Is a blank line missing after this section underline as well?
> +The driver source is located at:
> +
> +``drivers/scsi/leapraid/``
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1785823793.git.doubled@leap-io-kernel.com?part=2
next prev parent reply other threads:[~2026-08-04 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 7:02 [PATCH v5 0/2] scsi: Add LeapRAID driver support Dongdong Hao
2026-08-04 7:02 ` [PATCH v5 1/2] scsi: leapraid: Add new SCSI driver Dongdong Hao
2026-08-04 7:02 ` [PATCH v5 2/2] scsi: leapraid: Add driver documentation Dongdong Hao
2026-08-04 9:33 ` sashiko-bot [this message]
2026-08-07 16:00 ` [PATCH v5 0/2] scsi: Add LeapRAID driver support Martin K. Petersen (Oracle)
2026-08-09 8:47 ` Hao Dongdong
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=20260804093331.417E61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=doubled@leap-io-kernel.com \
--cc=linux-scsi@vger.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