From: Avri Altman <Avri.Altman@wdc.com>
To: "nitirawa@codeaurora.org" <nitirawa@codeaurora.org>
Cc: "asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"stummala@codeaurora.org" <stummala@codeaurora.org>,
"vbadigan@codeaurora.org" <vbadigan@codeaurora.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V1 0/3] scsi: ufs: Add a vops to configure VCC voltage level
Date: Mon, 8 Feb 2021 12:22:05 +0000 [thread overview]
Message-ID: <DM6PR04MB65757109C5292CD42F7799EAFC8F9@DM6PR04MB6575.namprd04.prod.outlook.com> (raw)
In-Reply-To: <2fb825d458fb87a522b4a64370ee83b1@codeaurora.org>
> >> The flow should be generic - isn't it?
> >> Why do you need the entire flow to be vendor-specific?
> >> Why not just the parameters vendor-specific?
> >>
> >> Thanks,
> >> Avri
> >
> > Hi Avri,
> > This vops change was done as per the below mail thread
> > discussion where it was decided to go with vops and
> > let vendors handle it, until specs provides more clarity.
> >
> > https://www.spinics.net/lists/kernel/msg3754995.html
> >
> > Regards,
> > Nitin
>
> Hi Avri,
> Please let me know if you have any further comments on this.
No further comments.
Looks like you need an ack from Stanley or Bjorn who proposed this approach.
Thanks,
Avri
next prev parent reply other threads:[~2021-02-08 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 16:54 [PATCH V1 0/3] scsi: ufs: Add a vops to configure VCC voltage level Nitin Rawat
2021-01-28 16:54 ` [PATCH V1 1/3] scsi: ufs: export api for use in vendor file Nitin Rawat
[not found] ` <DM6PR04MB657574D3D8B99F3A4997D810FCB79@DM6PR04MB6575.namprd04.prod.outlook.com>
2021-02-01 8:10 ` nitirawa
2021-01-28 16:54 ` [PATCH V1 2/3] scsi: ufs: add a vops to configure VCC voltage level Nitin Rawat
2021-01-28 16:54 ` [PATCH V1 3/3] scsi: ufs-qcom: configure VCC voltage level in vendor file Nitin Rawat
[not found] ` <DM6PR04MB6575D0348161330D21A9B6C5FCB79@DM6PR04MB6575.namprd04.prod.outlook.com>
2021-02-01 8:31 ` [PATCH V1 0/3] scsi: ufs: Add a vops to configure VCC voltage level nitirawa
2021-02-08 10:30 ` nitirawa
2021-02-08 12:22 ` Avri Altman [this message]
2021-02-19 13:29 ` nitirawa
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=DM6PR04MB65757109C5292CD42F7799EAFC8F9@DM6PR04MB6575.namprd04.prod.outlook.com \
--to=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=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nitirawa@codeaurora.org \
--cc=stanley.chu@mediatek.com \
--cc=stummala@codeaurora.org \
--cc=vbadigan@codeaurora.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).