From: Christoph Hellwig <hch@infradead.org>
To: jongmin jeong <jjmin.jeong@samsung.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
alim.akhtar@samsung.com, avri.altman@wdc.com,
cang@codeaurora.org, beanhuo@micron.com, adrian.hunter@intel.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi: ufs: add quirk to handle broken UIC command
Date: Thu, 27 May 2021 09:00:17 +0100 [thread overview]
Message-ID: <YK9RkXoLsUT38cTP@infradead.org> (raw)
In-Reply-To: <20210527030901.88403-2-jjmin.jeong@samsung.com>
On Thu, May 27, 2021 at 12:08:59PM +0900, jongmin jeong wrote:
> samsung ExynosAuto SoC has two types of host controller interface to
> support the virtualization of UFS Device.
> One is the physical host(PH) that the same as conventaional UFSHCI,
> and the other is the virtual host(VH) that support data transfer function only.
You forgot to include the hunk that actually sets the quirk.
Also please work on the commit log formatting.
> Change-Id: Ie528726b29bcb643149440bf1c90eaa5995c5ac1
This kind of crap has no business in a commit log.
next prev parent reply other threads:[~2021-05-27 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210527031217epcas2p44b9d999edcc55b345dfd0749acefeaec@epcas2p4.samsung.com>
2021-05-27 3:08 ` [PATCH 0/3] Add quirk to support exynos ufshci jongmin jeong
2021-05-27 3:08 ` [PATCH 1/3] scsi: ufs: add quirk to handle broken UIC command jongmin jeong
2021-05-27 8:00 ` Christoph Hellwig [this message]
2021-06-03 3:08 ` 정종민
2021-05-27 3:09 ` [PATCH 2/3] scsi: ufs: add quirk to enable host controller without interface configuration jongmin jeong
2021-05-27 3:09 ` [PATCH 3/3] scsi: ufs: add quirk to support host reset only jongmin jeong
2021-05-27 6:08 ` kernel test robot
2021-05-27 6:31 ` Can Guo
2021-05-27 6:53 ` Can Guo
2021-06-03 3:21 ` 정종민
2021-05-27 7:34 ` kernel test robot
2021-05-27 8:17 ` [PATCH 0/3] Add quirk to support exynos ufshci Alim Akhtar
2021-05-27 16:40 ` Bart Van Assche
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=YK9RkXoLsUT38cTP@infradead.org \
--to=hch@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=jjmin.jeong@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox