From: Adrian Hunter <adrian.hunter@intel.com>
To: Chanwoo Lee <cw9316.lee@samsung.com>,
riteshh@codeaurora.org, asutoshd@codeaurora.org,
ulf.hansson@linaro.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: grant.jung@samsung.com, jt77.jang@samsung.com,
dh0421.hwang@samsung.com, sh043.lee@samsung.com
Subject: Re: [PATCH] Unnecessary code change in spin_lock section.
Date: Mon, 17 May 2021 14:34:18 +0300 [thread overview]
Message-ID: <3a0ca4cc-5d5c-1cb2-8942-7f90da06e854@intel.com> (raw)
In-Reply-To: <20210513023307.12435-1-cw9316.lee@samsung.com>
On 13/05/21 5:33 am, Chanwoo Lee wrote:
> From: ChanWoo Lee <cw9316.lee@samsung.com>
>
> This is the spin_lock section for cq_host, and mmc setting is unnecessary.
>
> Signed-off-by: ChanWoo Lee <cw9316.lee@samsung.com>
> ---
> drivers/mmc/host/cqhci-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/host/cqhci-core.c b/drivers/mmc/host/cqhci-core.c
> index 93b0432bb601..4d76c858d45f 100644
> --- a/drivers/mmc/host/cqhci-core.c
> +++ b/drivers/mmc/host/cqhci-core.c
> @@ -1090,8 +1090,8 @@ static void cqhci_recovery_finish(struct mmc_host *mmc)
> spin_lock_irqsave(&cq_host->lock, flags);
> cq_host->qcnt = 0;
> cq_host->recovery_halt = false;
> - mmc->cqe_on = false;
> spin_unlock_irqrestore(&cq_host->lock, flags);
No, we don't want anyone to see mmc->cqe_on == true and
cq_host->recovery_halt == false at this point.
> + mmc->cqe_on = false;> /* Ensure all writes are done before interrupts are re-enabled */
> wmb();
>
prev parent reply other threads:[~2021-05-17 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210513023747epcas1p23502f390781d1a5a8f6512982af1fd65@epcas1p2.samsung.com>
2021-05-13 2:33 ` Chanwoo Lee
2021-05-17 11:34 ` Adrian Hunter [this message]
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=3a0ca4cc-5d5c-1cb2-8942-7f90da06e854@intel.com \
--to=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=cw9316.lee@samsung.com \
--cc=dh0421.hwang@samsung.com \
--cc=grant.jung@samsung.com \
--cc=jt77.jang@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=riteshh@codeaurora.org \
--cc=sh043.lee@samsung.com \
--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
all inboxes | Powered by JetHome®