Re: [PATCH 1/1] scsi: ufs: Print real incorrect request response code

2019-04-15 Thread Martin K. Petersen
Stanley, > If UFS device responds an unknown request response code, we can not > know what it was via logs because the code is replaced by "DID_ERROR > << 16" before log printing. > > Fix this to provide precise request response code information for > easier issue breakdown. Applied to 5.2/scsi

RE: [PATCH 1/1] scsi: ufs: Print real incorrect request response code

2019-04-15 Thread Winkler, Tomas
> On 4/15/19 5:23 AM, Stanley Chu wrote: > > If UFS device responds an unknown request response code, we can not > > know what it was via logs because the code is replaced by "DID_ERROR > > << 16" before log printing. > > > > Fix this to provide precise request response code information for > > ea

Re: [PATCH 1/1] scsi: ufs: Print real incorrect request response code

2019-04-15 Thread Bart Van Assche
On 4/15/19 5:23 AM, Stanley Chu wrote: > If UFS device responds an unknown request response code, > we can not know what it was via logs because the code > is replaced by "DID_ERROR << 16" before log printing. > > Fix this to provide precise request response code information > for easier issue bre

[PATCH 1/1] scsi: ufs: Print real incorrect request response code

2019-04-15 Thread Stanley Chu
If UFS device responds an unknown request response code, we can not know what it was via logs because the code is replaced by "DID_ERROR << 16" before log printing. Fix this to provide precise request response code information for easier issue breakdown. Signed-off-by: Stanley Chu --- drivers/s