On Fri, 2018-09-07 at 12:49 +-0300, Avri Altman wrote: +AD4 drivers/scsi/ufs/Kconfig +AHw 19 +-+-+- +AD4 drivers/scsi/ufs/Makefile +AHw 3 +- +AD4 drivers/scsi/ufs/ufs.h +AHw 30 ---- +AD4 drivers/scsi/ufs/ufs+AF8-bsg.c +AHw 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +AD4 drivers/scsi/ufs/ufs+AF8-bsg.h +AHw 67 +-+-+-+-+-+-+-+-+- +AD4 drivers/scsi/ufs/ufshcd.c +AHw 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------------ +AD4 ---- +AD4 drivers/scsi/ufs/ufshcd.h +AHw 8 +- +AD4 drivers/scsi/ufs/ufshci.h +AHw 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 +ACI-read the source+ACI is an acceptable answer. Thanks, Bart.
