From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kiwoong Kim <kwmad.kim@samsung.com>
Cc: linux-scsi@vger.kernel.org, cpgs@samsung.com,
HeonGwang Chu <hg.chu@samsung.com>
Subject: Re: [PATCH v4] ufs: introduce UFSHCD_QUIRK_PRDT_BYTE_GRAN quirk
Date: Tue, 22 Nov 2016 16:45:06 -0500 [thread overview]
Message-ID: <yq1zikrw5nh.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <01b501d24497$66a81e50$33f85af0$@samsung.com> (Kiwoong Kim's message of "Tue, 22 Nov 2016 17:06:59 +0900")
>>>>> "Kiwoong" == Kiwoong Kim <kwmad.kim@samsung.com> writes:
Hi Kiwoong,
Kiwoong> Some UFS host controllers may think granularities of PRDT
Kiwoong> length and offset as bytes, not double words.
Your patch still didn't apply cleanly to 4.10/scsi-queue. I did it by
hand. Please verify.
Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-11-22 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 8:06 [PATCH v4] ufs: introduce UFSHCD_QUIRK_PRDT_BYTE_GRAN quirk Kiwoong Kim
2016-11-22 21:45 ` Martin K. Petersen [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=yq1zikrw5nh.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=cpgs@samsung.com \
--cc=hg.chu@samsung.com \
--cc=kwmad.kim@samsung.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