From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Don Brace <don.brace@microchip.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Lee Duncan <lduncan@suse.com>, Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH v2 0/2] Fix SAS wildcard scan on smartpqi and other controllers
Date: Thu, 30 Apr 2026 12:30:36 -0400 [thread overview]
Message-ID: <yq1y0i4csyi.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260421202018.511388-1-mwilck@suse.com> (Martin Wilck's message of "Tue, 21 Apr 2026 22:20:16 +0200")
Martin,
> A lot of SAS drivers, including the affected ones, provide
> scan_start() and scan_finished() functions that offer custom,
> firmware-assisted scanning functionality specific for the driver in
> question. The idea of this patch set is to map the "wildcard scan" to
> this driver-specific scanning procedure if the driver provides one.
https://sashiko.dev/#/patchset/20260421202018.511388-1-mwilck%40suse.com
--
Martin K. Petersen
next prev parent reply other threads:[~2026-04-30 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 20:20 [PATCH v2 0/2] Fix SAS wildcard scan on smartpqi and other controllers Martin Wilck
2026-04-21 20:20 ` [PATCH v2 1/2] scsi: smartpqi: use shost_to_hba() in pqi_scan_finished() Martin Wilck
2026-04-21 20:20 ` [PATCH v2 2/2] scsi: sas_user_scan: use scan_start if available Martin Wilck
2026-04-30 16:30 ` Martin K. Petersen [this message]
2026-05-04 16:58 ` [PATCH v2 0/2] Fix SAS wildcard scan on smartpqi and other controllers Martin Wilck
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=yq1y0i4csyi.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=don.brace@microchip.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.wilck@suse.com \
--cc=mwilck@suse.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