From: Bart Van Assche <bvanassche@acm.org>
To: Yihang Li <liyihang9@huawei.com>,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, ranjan.kumar@broadcom.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
liuyonglong@huawei.com, linuxarm@huawei.com
Subject: Re: [PATCH] scsi: Fix the maximum channel scanning issue
Date: Mon, 16 Mar 2026 10:22:46 -0700 [thread overview]
Message-ID: <6103e5cd-12e2-4527-8aee-985c2a75f255@acm.org> (raw)
In-Reply-To: <20260313023057.4151105-1-liyihang9@huawei.com>
On 3/12/26 7:30 PM, Yihang Li wrote:
> Fix and support specifying the scan shost->max_channel for scanning.
A more specific prefix than "scsi:" should be used for SAS patches. In
the kernel log I found the following examples:
* scsi: transport: sas:
* scsi: scsi_transport_sas:
I'm not sure what prefix is preferred.
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-16 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 2:30 [PATCH] scsi: Fix the maximum channel scanning issue Yihang Li
2026-03-16 17:22 ` Bart Van Assche [this message]
2026-03-17 6:24 ` Yihang Li
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=6103e5cd-12e2-4527-8aee-985c2a75f255@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyihang9@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=ranjan.kumar@broadcom.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