[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d96b40d-fc83-9218-9479-3de423594ddb@huawei.com>
Date: Thu, 10 Jan 2019 09:11:44 +0000
From: John Garry <john.garry@...wei.com>
To: Christoph Hellwig <hch@....de>,
Logan Gunthorpe <logang@...tatee.com>
CC: <linux-scsi@...r.kernel.org>, <linux-block@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Intel SCU Linux support <intel-linux-scu@...el.com>,
Artur Paszkiewicz <artur.paszkiewicz@...el.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Jens Axboe <axboe@...nel.dk>, Jeff Moyer <jmoyer@...hat.com>,
chenxiang <chenxiang66@...ilicon.com>
Subject: Re: [PATCH] scsi: isci: initialize shost fully before calling
scsi_add_host()
On 09/01/2019 18:41, Christoph Hellwig wrote:
> This looks good. I wonder if there is any good way to prevent other
> drivers from picking up this bug byt using a better interface, but
> that should not delay your fix.
>
> .
>
I noticed that hisi_sas has this same problem but I forgot to fix it.
So how about just drop these APIs and let the user set the shost
protection parameters directly, like other shost parameters, which
should make it a bit clearer when these should be set, i.e. before
scsi_add_host()?
John
Powered by blists - more mailing lists