RE: [PATCH v4 0/7] scsi: ufs bsg endpoint

2018-09-16 Thread Avri Altman
> > On 09/15/18 23:41, Avri Altman wrote: > >> Since this patch series does not touch any include/uapi header and since no > >> uapi UFS header files already exist, how is user space software expected to > >> know which message format it should use for communicating over the UFS > BSG > >> endpoin

Re: [PATCH v4 0/7] scsi: ufs bsg endpoint

2018-09-16 Thread Bart Van Assche
On 09/15/18 23:41, Avri Altman wrote: Since this patch series does not touch any include/uapi header and since no uapi UFS header files already exist, how is user space software expected to know which message format it should use for communicating over the UFS BSG endpoint? I don't think that "re

RE: [PATCH v4 0/7] scsi: ufs bsg endpoint

2018-09-15 Thread Avri Altman
Hi Bart, > Since this patch series does not touch any include/uapi header and since no > uapi UFS header files already exist, how is user space software expected to > know which message format it should use for communicating over the UFS BSG > endpoint? I don't think that "read the source" is an a

Re: [PATCH v4 0/7] scsi: ufs bsg endpoint

2018-09-10 Thread Bart Van Assche
On Fri, 2018-09-07 at 12:49 +0300, Avri Altman wrote: > drivers/scsi/ufs/Kconfig | 19 +++ > drivers/scsi/ufs/Makefile | 3 + > drivers/scsi/ufs/ufs.h | 30 > drivers/scsi/ufs/ufs_bsg.c | 327 > drivers/scsi/ufs/ufs_bsg.h | 67 + >