From: Avri Altman <Avri.Altman@wdc.com>
To: Stanley Chu <stanley.chu@mediatek.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>
Cc: "beanhuo@micron.com" <beanhuo@micron.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kuohong.wang@mediatek.com" <kuohong.wang@mediatek.com>,
"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
"chun-hung.wu@mediatek.com" <chun-hung.wu@mediatek.com>,
"andy.teng@mediatek.com" <andy.teng@mediatek.com>
Subject: Re: [PATCH v1 0/3] scsi: ufs: pass device information to apply_dev_quirks
Date: Sun, 5 Jan 2020 05:51:14 +0000 [thread overview]
Message-ID: <MN2PR04MB69913F0B671032A388747CF7FC3D0@MN2PR04MB6991.namprd04.prod.outlook.com> (raw)
In-Reply-To: <1578200118-29547-1-git-send-email-stanley.chu@mediatek.com>
You have to squash patch 1 & 2, otherwise your patch 1 won't compile.
Other than that: looks good to me.
Thanks,
Avri
________________________________________
From: Stanley Chu <stanley.chu@mediatek.com>
Sent: Sunday, January 5, 2020 6:55:15 AM
To: linux-scsi@vger.kernel.org; martin.petersen@oracle.com; Avri Altman; alim.akhtar@samsung.com; jejb@linux.ibm.com
Cc: beanhuo@micron.com; asutoshd@codeaurora.org; cang@codeaurora.org; matthias.bgg@gmail.com; bvanassche@acm.org; linux-mediatek@lists.infradead.org; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; kuohong.wang@mediatek.com; peter.wang@mediatek.com; chun-hung.wu@mediatek.com; andy.teng@mediatek.com; Stanley Chu
Subject: [PATCH v1 0/3] scsi: ufs: pass device information to apply_dev_quirks
CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the sender and know that the content is safe.
Currently UFS driver has "global" device quirk scheme to allow driver applying
special handling for certain UFS devive models.
However some special device handlings are required for specific UFS hosts only
so it is better to make it happen in vendor's callbacks only to not "pollute"
common driver and common device quirks.
We already have apply_dev_quirks variant callback for vendors but lack of device
information for handling specific UFS device models. This series provides such
information to apply_dev_quirks callbacks, and applies related modifications.
Stanley Chu (3):
scsi: ufs: pass device information to apply_dev_quirks
scsi: ufs-qcom: modify apply_dev_quirks interface
scsi: ufs-mediatek: add apply_dev_quirks variant operation
drivers/scsi/ufs/ufs-mediatek.c | 11 +++++++++++
drivers/scsi/ufs/ufs-qcom.c | 3 ++-
drivers/scsi/ufs/ufshcd.c | 5 +++--
drivers/scsi/ufs/ufshcd.h | 7 ++++---
4 files changed, 20 insertions(+), 6 deletions(-)
--
2.18.0
next prev parent reply other threads:[~2020-01-05 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 4:55 [PATCH v1 0/3] scsi: ufs: pass device information to apply_dev_quirks Stanley Chu
2020-01-05 4:55 ` [PATCH v1 1/3] " Stanley Chu
2020-01-05 4:55 ` [PATCH v1 2/3] scsi: ufs-qcom: modify apply_dev_quirks interface Stanley Chu
2020-01-05 4:55 ` [PATCH v1 3/3] scsi: ufs-mediatek: add apply_dev_quirks variant operation Stanley Chu
2020-01-05 5:51 ` Avri Altman [this message]
2020-01-05 13:10 ` [PATCH v1 0/3] scsi: ufs: pass device information to apply_dev_quirks Stanley Chu
2020-01-05 16:40 ` Avri Altman
2020-01-06 0:26 ` Stanley Chu
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=MN2PR04MB69913F0B671032A388747CF7FC3D0@MN2PR04MB6991.namprd04.prod.outlook.com \
--to=avri.altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@mediatek.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;
as well as URLs for NNTP newsgroup(s).