On 2019-07-23 2:11 p.m., kbuild test robot wrote:
Hi Douglas, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on mkp-scsi/for-next] [also build test WARNING on v5.3-rc1 next-20190723] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
Hi, Well yes, you seem to be using the wrong git tree, or at least the wrong patchset. From the subject line above, I match that with a patchset sent to the linux-scsi list on 20190524. It contained both a rework of the existing driver plus new features outlined here: http://sg.danny.cz/sg/sg_v40.html It was suggested that I break that patchset in two, the first one being the existing driver rework. That patchset was sent to the linux-scsi list on 20190616 commencing with this subject line: "[PATCH 00/18] sg: add v4 interface". To date I have had no feedback for the later patchset so I have no idea whether the kbuild test robot has checked it or not. It is curious why yesterday, 6 weeks after the second patchset, robot messages start reappearing on a superseded patchset sent two months ago. The reported problems have already been dealt with (i.e. fixed). Work (mainly testing) continues on the "new features" patchset which I have structured on top of the "add v4 interface" patchset as patches 19 through 34. I see no point in sending a follow-on patchset with new features until the patchset sent on 20190616 is accepted. Doug Gilbert
