public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Julian Calaby <julian.calaby@gmail.com>,
	Joao Pinto <Joao.Pinto@synopsys.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	Christoph Hellwig <hch@infradead.org>, <gbroner@codeaurora.org>,
	<subhashj@codeaurora.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<CARLOS.PALMINHA@synopsys.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>
Subject: Re: [PATCH] add support for DWC UFS Host Controller
Date: Tue, 2 Feb 2016 14:47:31 +0000	[thread overview]
Message-ID: <56B0C183.3010509@synopsys.com> (raw)
In-Reply-To: <CAGRGNgWmjnf-fUqMEQ5K2sykdwk8dV9fkJv_0=Q5bz2CiqA-8Q@mail.gmail.com>

Hi,
In order to make a ufs-dwc-pci glue driver I will need to create a "pci driver
lib" like we have already for platform (ufshcd-pltfm.c). Should I call the
samsung glue driver ufs-samsung-pci.c which will use common pci functions from a
ufshcd-pci.c? Agree?

On 2/2/2016 11:49 AM, Julian Calaby wrote:
> Hi Joao,
> 
> On Tue, Feb 2, 2016 at 10:47 PM, Joao Pinto <Joao.Pinto@synopsys.com> wrote:
>>
>> Hi Julian,
>> I am already changing the architecture and I will send a v2 soon.
>> Thanks for the review.
> 
> Awesome, I look forward to it.
> 
> Thanks,
> 

Thanks.

Joao

  reply	other threads:[~2016-02-02 14:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 12:47 [PATCH] add support for DWC UFS Host Controller Joao Pinto
2016-02-02  1:00 ` Julian Calaby
2016-02-02 10:22   ` Joao Pinto
2016-02-02 11:44     ` Julian Calaby
2016-02-02 11:47       ` Joao Pinto
2016-02-02 11:49         ` Julian Calaby
2016-02-02 14:47           ` Joao Pinto [this message]
2016-02-02 22:27             ` Julian Calaby
  -- strict thread matches above, loose matches on Subject: below --
2016-02-01 12:55 Joao Pinto

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=56B0C183.3010509@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=akinobu.mita@gmail.com \
    --cc=gbroner@codeaurora.org \
    --cc=hch@infradead.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=julian.calaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=subhashj@codeaurora.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