From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Christoph Hellwig <hch@infradead.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Vinayak Holikatti <vinholikatti@gmail.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
Subhash Jadavani <subhashj@codeaurora.org>,
Santosh Yaragnavi <santosh.sy@samsung.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Szymon Mielczarek <szymonx.mielczarek@intel.com>,
Michal Potomski <michalx.potomski@intel.com>,
Grzegorz Janca <grzegorz.janca@intel.com>,
Joao Pinto <Joao.Pinto@synopsys.com>
Subject: Re: [PATCH V4 2/2] scsi: ufshcd-pci: Add Intel CNL support
Date: Thu, 8 Jun 2017 10:36:12 +0100 [thread overview]
Message-ID: <21c668c5-251a-bc19-f0ba-3826d3515145@synopsys.com> (raw)
In-Reply-To: <20170607131625.GB18252@infradead.org>
Hello to all,
Às 2:16 PM de 6/7/2017, Christoph Hellwig escreveu:
> On Tue, Jun 06, 2017 at 02:35:31PM +0300, Adrian Hunter wrote:
>> Add PCI id and variant ops for Intel CNL UFS host controller.
>
> Looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> It would be great if we could fold tc-dwc-g210-pci into ufshcd-pci the
> same way.
>
I have forward the suggestion to the person on charge of UFS driver maintenance
at Synopsys. We will definitely have a look at it!
Thanks,
Joao
next prev parent reply other threads:[~2017-06-08 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 11:35 [PATCH V4 0/2] scsi: ufshcd-pci: Add Intel CNL support Adrian Hunter
2017-06-06 11:35 ` [PATCH V4 1/2] scsi: ufshcd-pci: Fix PM config Adrian Hunter
2017-06-07 13:14 ` Christoph Hellwig
2017-06-06 11:35 ` [PATCH V4 2/2] scsi: ufshcd-pci: Add Intel CNL support Adrian Hunter
2017-06-07 13:16 ` Christoph Hellwig
2017-06-08 9:36 ` Joao Pinto [this message]
2017-06-13 1:08 ` [PATCH V4 0/2] " Martin K. Petersen
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=21c668c5-251a-bc19-f0ba-3826d3515145@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=adrian.hunter@intel.com \
--cc=grzegorz.janca@intel.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michalx.potomski@intel.com \
--cc=santosh.sy@samsung.com \
--cc=subhashj@codeaurora.org \
--cc=szymonx.mielczarek@intel.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;
as well as URLs for NNTP newsgroup(s).