summaryrefslogtreecommitdiffstats
path: root/mm/cma.c
diff options
context:
space:
mode:
authorFelipe Balbi <felipe.balbi@linux.intel.com>2017-03-08 13:56:37 +0200
committerFelipe Balbi <felipe.balbi@linux.intel.com>2017-03-08 13:56:37 +0200
commit35b2719e72d375f3e32c819858165668d948d5f2 (patch)
tree5697eef95418403861b2eb4f5e7b54534c1a6a60 /mm/cma.c
parentef5e2fa9f65befa12f1113c734602d2c1964d2a5 (diff)
downloadlinux-35b2719e72d375f3e32c819858165668d948d5f2.tar.bz2
usb: dwc3: gadget: make to increment req->remaining in all cases
Sometimes, we might get a completion for a TRB which is left with HWO bit. Even in these cases, we should increment req->remaining to properly report total transferred size. I noticed this while debuggin a separate problem seen with MSC tests from USBCV. Sometimes we would erroneously report a completion for a 512-byte transfer when, in reality, we transferred 0 bytes. Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'mm/cma.c')
0 files changed, 0 insertions, 0 deletions