From: Subhash Jadavani <subhashj@codeaurora.org>
To: Kiwoong Kim <kwmad.kim@samsung.com>
Cc: vinholikatti@gmail.com,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, 추헌광 <hg.chu@samsung.com>,
linux-scsi-owner@vger.kernel.org
Subject: Re: [PATCH v1 0/8] Support for Exynos specific UFS driver
Date: Thu, 06 Oct 2016 12:13:18 -0700 [thread overview]
Message-ID: <85ac557c49df48cc605813b04f3778f5@codeaurora.org> (raw)
In-Reply-To: <006301d21fa9$70aebe80$520c3b80$@samsung.com>
Hi Kim,
On 2016-10-06 01:12, Kiwoong Kim wrote:
> This series of patches introduce support for Exynos specific UFS
> driver.
> An original version of this has been applied on mass production
> of commercial mobile devices.
>
> Documentation/devicetree/bindings/ufs/ufs-exynos.txt | 93 +
> drivers/scsi/ufs/Kconfig | 10 +
> drivers/scsi/ufs/Makefile | 1 +
> drivers/scsi/ufs/mphy.h | 38
> +
> drivers/scsi/ufs/ufs-exynos.c | 2084
> ++++++++++++++++++++
> drivers/scsi/ufs/ufs-exynos.h | 621
> ++++++
> drivers/scsi/ufs/ufshcd.c | 146
> +-
> drivers/scsi/ufs/ufshcd.h | 62 +
> drivers/scsi/ufs/ufshci.h | 14
> +-
> drivers/scsi/ufs/unipro.h | 24 +
> 10 files changed, 3073 insertions(+), 20 deletions(-)
> create mode 100644
> Documentation/devicetree/bindings/ufs/ufs-exynos.txt
> create mode 100644 drivers/scsi/ufs/mphy.h
> create mode 100644 drivers/scsi/ufs/ufs-exynos.c
> create mode 100644 drivers/scsi/ufs/ufs-exynos.h
This supposed to be 8-patch series but i only patch #1 (subject: [PATCH
v1 1/8] ufs: add some vendor specific operations) on mailing list. Can
you please send out the full patch series?
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-06 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 8:12 [PATCH v1 0/8] Support for Exynos specific UFS driver Kiwoong Kim
2016-10-06 19:13 ` Subhash Jadavani [this message]
2016-10-07 1:19 ` Kiwoong Kim
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=85ac557c49df48cc605813b04f3778f5@codeaurora.org \
--to=subhashj@codeaurora.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hg.chu@samsung.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vinholikatti@gmail.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