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 +++++++++
>  drivers/scsi/ufs/ufshcd.c  | 362 ++++++++++++++++++++++++++++++-----------
> ----
>  drivers/scsi/ufs/ufshcd.h  |   8 +
>  drivers/scsi/ufs/ufshci.h  |  25 ++--

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 acceptable answer.

Thanks,

Bart.

Reply via email to