On 11/25/2016 3:37 PM, Adrian Hunter wrote:
mmc_start_req() assumes it is never called with the new request already prepared. That is true if the queue consists of only 2 requests, but is not true for a longer queue. e.g. mmc_start_req() has a current and previous request but still exits to queue a new request if the queue size is greater than 2. In that case, when mmc_start_req() is called again, the current request will have been prepared already. Fix by flagging if the request has been prepared. That also means ensuring that struct mmc_async_req is always initialized to zero, which wasn't the case in mmc_test. Signed-off-by: Adrian Hunter <adrian.hunter@xxxxxxxxx>
Looks good! Reviewed-by: Harjani Ritesh <riteshh@xxxxxxxxxxxxxx> Regards Ritesh -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
