> On Oct 3, 2017, at 3:48 AM, Christoph Hellwig wrote:
>
> Always use bsg_job->reply instead of scsi_req(bsg_job->req)->sense), as
> they always point to the same memory.
>
> Never set scsi_req(bsg_job->req)->result and we'll set that value through
> bsg_job_done.
>
> Signed-off-by: Christoph
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Ke
On 10/03/2017 12:48 PM, Christoph Hellwig wrote:
> Always use bsg_job->reply instead of scsi_req(bsg_job->req)->sense), as
> they always point to the same memory.
>
> Never set scsi_req(bsg_job->req)->result and we'll set that value through
> bsg_job_done.
>
> Signed-off-by: Christoph Hellwig
>
Always use bsg_job->reply instead of scsi_req(bsg_job->req)->sense), as
they always point to the same memory.
Never set scsi_req(bsg_job->req)->result and we'll set that value through
bsg_job_done.
Signed-off-by: Christoph Hellwig
---
drivers/scsi/qla2xxx/qla_bsg.c | 10 --
drivers/scsi
4 matches
Mail list logo