All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Bunker <brian@purestorage.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v2 0/3] Rework the struct scsi_device inquiry information
Date: Mon, 18 May 2026 11:17:49 -0700	[thread overview]
Message-ID: <20260518181749.28686-1-brian@purestorage.com> (raw)
In-Reply-To: <20260515205222.1754621-1-bvanassche@acm.org>

Tested this series on top of v7.1-rc3 on a host attached to a
Pure FlashArray, with 10 LUNs presented over 4 paths each (40 sd
nodes total):

  - Build clean.
  - SCSI scan completes normally; dmesg clean.
  - /sys/class/scsi_device/H:C:T:L/device/{vendor,model,rev} are
    byte-identical to the pre-patch kernel.
  - Multipath continues to enumerate and bind devices correctly.

Tested-by: Brian Bunker <brian@purestorage.com>

Thanks for taking this on.

Brian

  parent reply	other threads:[~2026-05-18 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 20:52 [PATCH v2 0/3] Rework the struct scsi_device inquiry information Bart Van Assche
2026-05-15 20:52 ` [PATCH v2 1/3] scsi: core, target: Add INQUIRY-related constants into <scsi/scsi_common.h> Bart Van Assche
2026-05-15 20:52 ` [PATCH v2 2/3] scsi: core: Use the INQUIRY-related constants Bart Van Assche
2026-05-15 20:52 ` [PATCH v2 3/3] scsi: core: Convert INQUIRY information Bart Van Assche
2026-05-18 18:17 ` Brian Bunker [this message]
2026-05-23  1:50 ` [PATCH v2 0/3] Rework the struct scsi_device inquiry information Martin K. Petersen
2026-06-02  2:10 ` Martin K. Petersen

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=20260518181749.28686-1-brian@purestorage.com \
    --to=brian@purestorage.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=martin.petersen@oracle.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 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.