Message ID | 20190401211712.19012-1-bsd@redhat.com |
---|---|
Headers | show |
Series | misc usb-mtp fixes | expand |
On Mon, 1 Apr 2019 at 22:17, Bandan Das <bsd@redhat.com> wrote: > > v4: > Added 1/3: <jpgva0nuddm.fsf@linux.bootlegged.copy> > v3: > 2/2: Fix indentation > Add back sending RES_OK for success > v2: > 1/2: Add Reviewed-by tag > 2/2: remove extra vars and directly call usb_mtp_queue_result > > The first patch removes a unnecessary function > and the second is just a code reorg of usb_mtp_write_data > to make it less confusing. Applies on top of > [PATCH v3] usb-mtp: fix return status of delete > Message-ID: > > Bandan Das (3): > usb-mtp: fix return status of delete > usb-mtp: remove usb_mtp_object_free_one > usb-mtp: refactor the flow of usb_mtp_write_data Hi Bandan, Gerd -- what's the status of this patchset? I think this is the one that fixes the CID1399415 Coverity issue about usb_mtp_write_data() return values, right? thanks -- PMM
> > Bandan Das (3): > > usb-mtp: fix return status of delete > > usb-mtp: remove usb_mtp_object_free_one > > usb-mtp: refactor the flow of usb_mtp_write_data > > Hi Bandan, Gerd -- what's the status of this patchset? > I think this is the one that fixes the CID1399415 > Coverity issue about usb_mtp_write_data() return values, right? 1+2 fixes where merged during 4.0 freeze, 3 left for post-freeze. It can follow now, queued up, next usb pull will have it. thanks for the reminder, Gerd