From: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
To: adrian.hunter@intel.com, ulf.hansson@linaro.org
Cc: stummala@codeaurora.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
Subject: [PATCH V1 0/2] CQE fixes
Date: Wed, 6 May 2020 20:04:01 +0530 [thread overview]
Message-ID: <1588775643-18037-1-git-send-email-vbadigan@codeaurora.org> (raw)
Fixes for a couple of issues observed with CQE. One with CQE completion
path and the other one is with CQE recovery path.
Sarthak Garg (1):
mmc: core: Fix recursive locking issue in CQE recovery path
Veerabhadrarao Badiganti (1):
mmc: core: Check request type before completing the request
drivers/mmc/core/block.c | 3 ++-
drivers/mmc/core/queue.c | 11 ++++++-----
2 files changed, 8 insertions(+), 6 deletions(-)
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc., is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next reply other threads:[~2020-05-06 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 14:34 Veerabhadrarao Badiganti [this message]
2020-05-06 14:34 ` [PATCH V1 1/2] mmc: core: Check request type before completing the request Veerabhadrarao Badiganti
2020-05-06 17:06 ` Adrian Hunter
2020-05-08 8:12 ` Ulf Hansson
2020-05-06 14:34 ` [PATCH V1 2/2] mmc: core: Fix recursive locking issue in CQE recovery path Veerabhadrarao Badiganti
2020-05-07 11:48 ` Adrian Hunter
2020-05-07 14:06 ` [PATCH] mmc: block: Fix request completion in the CQE timeout path Adrian Hunter
2020-05-08 5:25 ` Ulf Hansson
2020-05-08 6:22 ` [PATCH RESEND] " Adrian Hunter
2020-05-08 8:17 ` Ulf Hansson
2020-05-07 16:15 ` [PATCH V2] mmc: core: Fix recursive locking issue in CQE recovery path Veerabhadrarao Badiganti
2020-05-07 17:21 ` Adrian Hunter
2020-05-08 8:12 ` Ulf Hansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1588775643-18037-1-git-send-email-vbadigan@codeaurora.org \
--to=vbadigan@codeaurora.org \
--cc=adrian.hunter@intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).