From: Jinyoung CHOI <j-young.choi@samsung.com>
To: ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH v4 7/7] scsi: ufs: wb: Move the comment to the right position
Date: Wed, 27 Jul 2022 16:12:49 +0900 [thread overview]
Message-ID: <20220727071249epcms2p4f014deb4b3eef7d37f810bc26b1160e7@epcms2p4> (raw)
In-Reply-To: <20220727071143epcms2p4936513ee2d020b914db53f438445801a@epcms2p4>
The location of the comment is wrong. so fix it.
Reviewed-by: Avri Altman <avri.altman@wdc.com>
Signed-off-by: Jinyoung Choi <j-young.choi@samsung.com>
---
drivers/ufs/core/ufshcd.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
index c91010fb2105..cc149f78f38f 100644
--- a/drivers/ufs/core/ufshcd.c
+++ b/drivers/ufs/core/ufshcd.c
@@ -1298,9 +1298,10 @@ static int ufshcd_devfreq_scale(struct ufs_hba *hba, bool scale_up)
}
}
- /* Enable Write Booster if we have scaled up else disable it */
downgrade_write(&hba->clk_scaling_lock);
is_writelock = false;
+
+ /* Enable Write Booster if we have scaled up else disable it */
ufshcd_wb_toggle(hba, scale_up);
out_unprepare:
--
2.25.1
next prev parent reply other threads:[~2022-07-27 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p6>
2022-07-27 6:59 ` [PATCH v4 0/7] scsi: ufs: wb: Add sysfs attribute and cleanup Jinyoung CHOI
[not found] ` <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p8>
2022-07-27 7:07 ` [PATCH v4 3/7] scsi: ufs: wb: Change functions name and modify Jinyoung CHOI
2022-07-28 6:21 ` RE:(2) [PATCH v4 1/7] scsi: ufs: wb: Move ufshcd_is_wb_allowed() to callee Jinyoung CHOI
[not found] ` <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p5>
2022-07-27 7:04 ` Jinyoung CHOI
2022-07-27 13:16 ` Bean Huo
2022-07-27 7:05 ` [PATCH v4 2/7] scsi: ufs: wb: Change wb_enabled condition test Jinyoung CHOI
2022-07-27 13:49 ` Bean Huo
2022-07-27 7:08 ` [PATCH v4 4/7] scsi: ufs: wb: Add explicit flush sysfs attribute Jinyoung CHOI
2022-07-27 17:43 ` Bean Huo
[not found] ` <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p3>
2022-07-28 0:54 ` Jinyoung CHOI
[not found] ` <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p4>
2022-07-27 7:11 ` [PATCH v4 6/7] scsi: ufs: wb: Modify messages Jinyoung CHOI
2022-07-27 7:12 ` Jinyoung CHOI [this message]
[not found] ` <CGME20220727065904epcms2p60a7a56101785ddefa55c82b3cc25116d@epcms2p7>
2022-07-27 7:10 ` [PATCH v4 5/7] scsi: ufs: wb: Add ufshcd_is_wb_buf_flush_allowed() Jinyoung CHOI
2022-07-27 17:50 ` Bean Huo
2022-07-27 19:44 ` Bart Van Assche
2022-07-28 1:18 ` Jinyoung CHOI
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=20220727071249epcms2p4f014deb4b3eef7d37f810bc26b1160e7@epcms2p4 \
--to=j-young.choi@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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®