From: 서호영 <hy50.seo@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<beanhuo@micron.com>, <asutoshd@codeaurora.org>,
<cang@codeaurora.org>, <bvanassche@acm.org>,
<grant.jung@samsung.com>
Subject: RE: [RFC PATCH v3 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable write booster
Date: Mon, 27 Jul 2020 20:27:39 +0900 [thread overview]
Message-ID: <074001d66408$efdc5a80$cf950f80$@samsung.com> (raw)
In-Reply-To: <SN6PR04MB4640B30915D3D402B3B47F79FC720@SN6PR04MB4640.namprd04.prod.outlook.com>
>
> >
> > > This patch is not really needed - just squash it to the previous one.
> > Why you said this patch is not really needed?
> > I don't understand
> > Our WB device need to disable WB when called
> > ufshcd_reset_and_restore() func.
> > Please explain reason.
> This patch only change the names of some functions defined in the first
> patch.
> Squash it to the first one.
"Asutosh Das (asd) <asutoshd@codeaurora.org>" said this function not clearly.
So I modify this function name.
I think this name is clear than the previous name.
next prev parent reply other threads:[~2020-07-27 11:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200721095644epcas2p4aa2e620257686679e6c9e58ccabeac34@epcas2p4.samsung.com>
2020-07-21 9:57 ` [RFC PATCH v3 0/3] Support vendor specific operations for WB SEO HOYOUNG
2020-07-21 9:57 ` [RFC PATCH v3 1/3] scsi: ufs: modify write booster SEO HOYOUNG
2020-07-26 6:30 ` Avri Altman
2020-07-27 9:57 ` 서호영
2020-07-27 10:10 ` Avri Altman
2020-07-27 11:28 ` 서호영
2020-07-21 9:57 ` [RFC PATCH v3 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable " SEO HOYOUNG
2020-07-26 6:31 ` Avri Altman
2020-07-27 10:01 ` 서호영
2020-07-27 10:12 ` Avri Altman
2020-07-27 11:27 ` 서호영 [this message]
2020-07-27 11:29 ` Avri Altman
2020-07-27 11:33 ` 서호영
2020-07-21 9:57 ` [RFC PATCH v3 3/3] scsi: ufs: add vendor specific " SEO HOYOUNG
2020-07-26 6:39 ` Avri Altman
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='074001d66408$efdc5a80$cf950f80$@samsung.com' \
--to=hy50.seo@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=grant.jung@samsung.com \
--cc=jejb@linux.ibm.com \
--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 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.