On Mon, Apr 2, 2018 at 8:55 PM, Bart Van Assche wrote:
> On Mon, 2018-04-02 at 11:53 +0530, Sreekanth Reddy wrote:
>> On Fri, Mar 30, 2018 at 5:29 PM, Christoph Hellwig
>> wrote:
>> > On Fri, Mar 30, 2018 at 03:07:12PM +0530, Chaitra P B wrote:
>> > >
On Mon, Apr 2, 2018 at 10:29 AM, Douglas Gilbert wrote:
> On 2018-04-02 11:34 AM, Tim Walker wrote:
>>
>> On Sat, Mar 31, 2018 at 10:52 AM, Douglas Gilbert
>> wrote:
>>>
>>> On 2018-03-30 04:01 PM, Bart Van Assche wrote:
On Fri,
On 2018-04-02 11:34 AM, Tim Walker wrote:
On Sat, Mar 31, 2018 at 10:52 AM, Douglas Gilbert wrote:
On 2018-03-30 04:01 PM, Bart Van Assche wrote:
On Fri, 2018-03-30 at 12:36 -0600, Tim Walker wrote:
Yes I will be there to discuss the multi-LUN approach. I wanted to
On Sat, Mar 31, 2018 at 10:52 AM, Douglas Gilbert wrote:
> On 2018-03-30 04:01 PM, Bart Van Assche wrote:
>>
>> On Fri, 2018-03-30 at 12:36 -0600, Tim Walker wrote:
>>>
>>> Yes I will be there to discuss the multi-LUN approach. I wanted to get
>>> these interface details
On Mon, 2018-04-02 at 11:53 +0530, Sreekanth Reddy wrote:
> On Fri, Mar 30, 2018 at 5:29 PM, Christoph Hellwig wrote:
> > On Fri, Mar 30, 2018 at 03:07:12PM +0530, Chaitra P B wrote:
> > > Check scsi tracker for NULL before accessing it.
> > > And in some places there are
On Mon, 2018-04-02 at 20:09 +0530, Chaitra Basappa wrote:
> Below set of patches were prepared against Martin's 4.17/scsi-queue. Also
> today I tried applying patches to Martin's 4.17/scsi-queue and patches got
> applied smoothly, didn't observe any issue.
> Please share the observed errors/hunks
Bart,
Below set of patches were prepared against Martin's 4.17/scsi-queue. Also
today I tried applying patches to Martin's 4.17/scsi-queue and patches got
applied smoothly, didn't observe any issue.
Please share the observed errors/hunks failed messages.
Below is the link of the repo used by me:
On Mon, 2018-04-02 at 11:37 +0200, Johannes Thumshirn wrote:
> Coverity reports that we're assigning shost->use_blk_mq twice. This
> looks like the result of a bad merge of commit 2f31115e940c ("scsi:
> core: introduce force_blk_mq")
>
> Signed-off-by: Johannes Thumshirn
>
From: Xiubo Li
This patch adds 1 tcmu attr to reset and complete all the blocked
netlink waiting threads. It's used when the userspace daemon like
tcmu-runner has crashed or forced to shutdown just before the
netlink requests be replied to the kernel, then the netlink
Hello,
I am RAID HBA driver engineer here at Microsemi. We are working on linux driver
development for Microsemi SAS/SATA RAID HBA controllers.
As per our understanding, while a drive is processing the SANITIZE command:
- The drive should still be exposed to the OS.
- The drive will fail all
Hi Can,
On 3/2/2018 1:48 PM, Can Guo wrote:
From: Venkat Gopalakrishnan
Qcom ufs controller v3.1.0 supports 2 lanes, add support
to configure 2 lanes during phy initialization.
Signed-off-by: Venkat Gopalakrishnan
Signed-off-by: Subhash
Coverity reports that we're assigning shost->use_blk_mq twice. This
looks like the result of a bad merge of commit 2f31115e940c ("scsi:
core: introduce force_blk_mq")
Signed-off-by: Johannes Thumshirn
---
drivers/scsi/hosts.c | 1 -
1 file changed, 1 deletion(-)
diff --git
Bart,
Agreed and patches will be posted with below changes.
Thanks,
Chaitra
-Original Message-
From: Bart Van Assche [mailto:bart.vanass...@wdc.com]
Sent: Friday, March 30, 2018 10:05 PM
To: chaitra.basa...@broadcom.com; linux-scsi@vger.kernel.org
Cc: sathya.prak...@broadcom.com;
Bart,
Agreed with below changes, we will be posting the patches soon.
-Original Message-
From: Bart Van Assche [mailto:bart.vanass...@wdc.com]
Sent: Friday, March 30, 2018 9:46 PM
To: chaitra.basa...@broadcom.com; linux-scsi@vger.kernel.org
Cc: sathya.prak...@broadcom.com;
On Fri, Mar 30, 2018 at 5:29 PM, Christoph Hellwig wrote:
> On Fri, Mar 30, 2018 at 03:07:12PM +0530, Chaitra P B wrote:
>> Check scsi tracker for NULL before accessing it.
>> And in some places there are possibilities for getting valid st
>> but still other fields are not
On 2018/4/2 13:29, Sergey Senozhatsky wrote:
On (04/02/18 13:14), wen.yan...@zte.com.cn wrote:
> It's true that this print for the same device is useless. But it's
> useful for different devices. Is it possible to limit the print only
> for the same device?
In our scene,
On 2018/4/2 13:14, wen.yan...@zte.com.cn wrote:
Hello,
> It's true that this print for the same device is useless. But it's
> useful for different devices. Is it possible to limit the print only
> for the same device?
In our scene, it's just for the same device (q->queuedata), Thanks.
17 matches
Mail list logo