Re: [PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-10-09 Thread Grant Grundler
Awesome! Thanks Ulf! :) cheers grant On Mon, Oct 5, 2015 at 3:55 AM, Ulf Hansson wrote: > On 24 September 2015 at 03:30, Grant Grundler wrote: >> MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on >> any eMMC errors. However, in case there is any resp[] data, we >> should

Re: [PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-10-09 Thread Grant Grundler
Awesome! Thanks Ulf! :) cheers grant On Mon, Oct 5, 2015 at 3:55 AM, Ulf Hansson wrote: > On 24 September 2015 at 03:30, Grant Grundler wrote: >> MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on >> any eMMC errors. However, in

Re: [PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-10-05 Thread Ulf Hansson
On 24 September 2015 at 03:30, Grant Grundler wrote: > MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on > any eMMC errors. However, in case there is any resp[] data, we > should attempt to copy resp[] back to user space. The user app > can then determine which command(s) failed

Re: [PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-10-05 Thread Ulf Hansson
On 24 September 2015 at 03:30, Grant Grundler wrote: > MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on > any eMMC errors. However, in case there is any resp[] data, we > should attempt to copy resp[] back to user space. The user app > can then determine

[PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-09-23 Thread Grant Grundler
MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on any eMMC errors. However, in case there is any resp[] data, we should attempt to copy resp[] back to user space. The user app can then determine which command(s) failed in the MMC_IOC_MULTI_CMD case AND/OR report better diagnostics

[PATCH] mmc: block: copy resp[] data on err for MMC_IOC_MULTI_CMD

2015-09-23 Thread Grant Grundler
MMC_IOC_CMD and MMC_IOC_MULTI_CMD ioctl() code currently bails on any eMMC errors. However, in case there is any resp[] data, we should attempt to copy resp[] back to user space. The user app can then determine which command(s) failed in the MMC_IOC_MULTI_CMD case AND/OR report better diagnostics