Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH RESEND] scsi: Consistently define pci_device_ids using named initializers
Date: Wed, 11 Nov 2026 18:54:03 +0000	[thread overview]
Message-ID: <sashiko-outbox-209503@kernel.org> (raw)
In-Reply-To: <20261111183844.1906794-2-u.kleine-koenig@baylibre.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] scsi: stex: shifted model comments in stex_pci_tbl mislabel
  st_P3 PCI IDs
--

commit db5880bd5d82ae26b6fc5fffb19956c877343ba5
Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>

scsi: Consistently define pci_device_ids using named initializers

This commit converts struct pci_device_id arrays across SCSI drivers to use
PCI_DEVICE*() helper macros and named initializers for fields such as
.driver_data, .class, and .class_mask.

> diff --git a/drivers/scsi/stex.c b/drivers/scsi/stex.c
> index d4899816f7dc8..057aa4b026740 100644
> --- a/drivers/scsi/stex.c
> +++ b/drivers/scsi/stex.c
> @@ -1489,47 +1489,80 @@ static const struct scsi_host_template driver_template = {

[ ... ]

>  	/* st_P3, pluto */
> -	{ PCI_VENDOR_ID_PROMISE, 0x8870, PCI_VENDOR_ID_PROMISE,
> -		0x8870, 0, 0, st_P3 },
> -	/* st_P3, p3 */
> -	{ PCI_VENDOR_ID_PROMISE, 0x8870, PCI_VENDOR_ID_PROMISE,
> -		0x4300, 0, 0, st_P3 },
> -
> -	/* st_P3, SymplyStor4E */
> -	{ PCI_VENDOR_ID_PROMISE, 0x8871, PCI_VENDOR_ID_PROMISE,
> -		0x4311, 0, 0, st_P3 },
> -	/* st_P3, SymplyStor8E */
> -	{ PCI_VENDOR_ID_PROMISE, 0x8871, PCI_VENDOR_ID_PROMISE,
> -		0x4312, 0, 0, st_P3 },
> +	{
> +		/* st_P3, p3 */
> +		PCI_VDEVICE_SUB(PROMISE, 0x8870, PCI_VENDOR_ID_PROMISE, 0x8870),
> +		.driver_data = st_P3,
> +	}, {
> +		/* st_P3, SymplyStor4E */
> +		PCI_VDEVICE_SUB(PROMISE, 0x8870, PCI_VENDOR_ID_PROMISE, 0x4300),
> +		.driver_data = st_P3,
> +	}, {
> +		/* st_P3, SymplyStor8E */
> +		PCI_VDEVICE_SUB(PROMISE, 0x8871, PCI_VENDOR_ID_PROMISE, 0x4311),
> +		.driver_data = st_P3,
> +	}, {
> +		PCI_VDEVICE_SUB(PROMISE, 0x8871, PCI_VENDOR_ID_PROMISE, 0x4312),
> +		.driver_data = st_P3,
> +	},

[Severity: Low]
This isn't a bug, but placing the opening brace of the 0x8870/0x8870 entry
between the pluto and p3 comments shifts the model comments for these four
st_P3 entries by one element, mislabeling 0x8870/0x8870, 0x8870/0x4300, and
0x8871/0x4311 and leaving 0x8871/0x4312 uncommented.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111183844.1906794-2-u.kleine-koenig@baylibre.com?part=1

      reply	other threads:[~2026-11-11 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 18:38 [PATCH RESEND] scsi: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-11-11 18:54 ` 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=sashiko-outbox-209503@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=target-devel@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.com \
    /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