From: "Kiwoong Kim" <kwmad.kim@samsung.com>
To: "'Avri Altman'" <Avri.Altman@wdc.com>, <linux-scsi@vger.kernel.org>
Subject: RE: [RFC PATCH v1 0/2] permit vendor specific timeouts for PMC
Date: Sat, 19 Dec 2020 11:55:11 +0900 [thread overview]
Message-ID: <003701d6d5b2$5e51c340$1af549c0$@samsung.com> (raw)
In-Reply-To: <DM6PR04MB65754CF9B01B346840FF98A2FCC30@DM6PR04MB6575.namprd04.prod.outlook.com>
> > There are some attribute settings before power mode change in ufshcd.c
> > that should be variant per vendor.
> But you've added a quirk, which is not what your commit log say.
> If indeed unipro allows to skip/set values other than default - add the
> appropriate vop.
> Otherwise, if it's just a non-standard behavior of exynos - then your
> patch is appropriate, But you need to reword your commit log: both here
> and in your 1/2 patch.
>
> Also, you forgot to remove the gerrit change-id.
>
> Thanks,
> Avri
You're right and for change-id, there might be something wrong in my local branch.
Anyway thanks !
Thanks.
Kiwoong Kim
> >
> > Kiwoong Kim (2):
> > ufs: add a quirk for vendor specifics before pmc
> > ufs: ufs-exynos: apply vendor specifics for three timeouts
> >
> > drivers/scsi/ufs/ufs-exynos.c | 8 +++++++-
> > drivers/scsi/ufs/ufshcd.c | 40 +++++++++++++++++++++----------------
> ---
> > drivers/scsi/ufs/ufshcd.h | 6 ++++++
> > 3 files changed, 34 insertions(+), 20 deletions(-)
> >
> > --
> > 2.7.4
prev parent reply other threads:[~2020-12-19 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201218074142epcas2p4c5f276e54ff896b8e990303376a15154@epcas2p4.samsung.com>
2020-12-18 7:30 ` [RFC PATCH v1 0/2] permit vendor specific timeouts for PMC Kiwoong Kim
2020-12-18 7:30 ` [RFC PATCH v1 1/2] ufs: add a quirk for vendor specifics before pmc Kiwoong Kim
2020-12-18 7:30 ` [RFC PATCH v1 2/2] ufs: ufs-exynos: apply vendor specifics for three timeouts Kiwoong Kim
2020-12-18 13:33 ` [RFC PATCH v1 0/2] permit vendor specific timeouts for PMC Avri Altman
2020-12-19 2:55 ` Kiwoong Kim [this message]
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='003701d6d5b2$5e51c340$1af549c0$@samsung.com' \
--to=kwmad.kim@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=linux-scsi@vger.kernel.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