From: "Bean Huo (beanhuo)" <beanhuo@micron.com>
To: Avri Altman <Avri.Altman@wdc.com>,
Can Guo <cang@qti.qualcomm.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"nguyenb@codeaurora.org" <nguyenb@codeaurora.org>,
"rnayak@codeaurora.org" <rnayak@codeaurora.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"kernel-team@android.com" <kernel-team@android.com>,
"saravanak@google.com" <saravanak@google.com>,
"salyzyn@google.com" <salyzyn@google.com>,
"cang@codeaurora.org" <cang@codeaurora.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Stanley Chu <stanley.chu@mediatek.com>,
open list <linux-kernel@vger.kernel.org>
Subject: RE: [EXT] RE: [PATCH v3 2/4] scsi: ufs: Update VCCQ2 and VCCQ min/max voltage hard codes
Date: Wed, 27 Nov 2019 12:40:50 +0000 [thread overview]
Message-ID: <BN7PR08MB5684DDB115B1F27D7D98A978DB440@BN7PR08MB5684.namprd08.prod.outlook.com> (raw)
In-Reply-To: <MN2PR04MB6991F3919641BB0F60BAA03CFC450@MN2PR04MB6991.namprd04.prod.outlook.com>
> > voltage range is 1.14v ~ 1.26v. Update their hard codes accordingly to
> > make sure they work in a safe range compliant for ver
> > 1.0/1.1/2.0/2.1/3.0 UFS devices.
> >
> > Signed-off-by: Can Guo <cang@codeaurora.org>
> Reviewed-by Avri Altman <avri.altman@wdc.com>
Hi, Avri
Your review tag string missed a colon, which results in cannot mark R in patchwork.
Reviewed-by: Bean Huo <beanhuo@micron.com>
next prev parent reply other threads:[~2019-11-27 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 6:53 [PATCH v3 0/4] UFS driver general fixes bundle 5 Can Guo
2019-11-26 6:53 ` [PATCH v3 1/4] scsi: ufs: Recheck bkops level if bkops is disabled Can Guo
2019-11-26 6:53 ` [PATCH v3 2/4] scsi: ufs: Update VCCQ2 and VCCQ min/max voltage hard codes Can Guo
2019-11-26 7:13 ` Avri Altman
2019-11-27 12:40 ` Bean Huo (beanhuo) [this message]
[not found] ` <0101016ec4ca5743-ec27a8f4-b0cd-427b-a65e-e6a26b10d45a-000000@us-west-2.amazonses.com>
2019-12-02 7:44 ` Avri Altman
2019-11-26 6:53 ` [PATCH v3 3/4] scsi: ufs: Avoid messing up the compl_time_stamp of lrbs Can Guo
2019-11-26 6:53 ` [PATCH v3 4/4] scsi: ufs: Complete pending requests in host reset and restore path Can Guo
2019-12-10 0:47 ` [PATCH v3 0/4] UFS driver general fixes bundle 5 Martin K. Petersen
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=BN7PR08MB5684DDB115B1F27D7D98A978DB440@BN7PR08MB5684.namprd08.prod.outlook.com \
--to=beanhuo@micron.com \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=cang@qti.qualcomm.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=pedrom.sousa@synopsys.com \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.