linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: JC Kuo <jckuo@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: <jonathanh@nvidia.com>, <linux-tegra@vger.kernel.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <nkristam@nvidia.com>,
	<skomatineni@nvidia.com>
Subject: Re: [PATCH v3 0/7] add Tegra194 XUSB host and pad controller support
Date: Wed, 9 Oct 2019 10:23:11 +0800	[thread overview]
Message-ID: <454e29a6-bf31-c75c-0f29-abd18a4ae071@nvidia.com> (raw)
In-Reply-To: <20191008112907.GC228118@ulmo>

On 10/8/19 7:29 PM, Thierry Reding wrote:
> On Mon, Oct 07, 2019 at 01:03:11PM +0200, Greg KH wrote:
>> On Sat, Oct 05, 2019 at 12:28:59AM +0800, JC Kuo wrote:
>>> Hi,
>>>
>>> This series introduces support for Tegra194 XUSB host and pad
>>> controller. Tegra194 XUSB host and pad controller are highly
>>> similar to the controllers found on Tegra186. Therefore, it's
>>> possible to resue xhci-tegra.c and xusb-tegra186.c for Tegra194.
>>
>> I've taken patches 1 and 2 through my USB tree.  If you want/need me to
>> take the others, please get acks from those maintainers on them so I can
>> do so.
> 
> I can pick up patches 6 and 7 into the Tegra tree. There are a few
> patches in there already that conflict with the DT changes in this
> series and those will be easier to resolve in the Tegra tree.
> 
> JC, I noticed that you didn't Cc Kishon as the PHY subsystem maintainer.
> Please resend the series with Kishon added in the To: line to make sure
> he sees them and can apply or ack them.
> 
> Given that Greg's already applied patches 1 and 2, maybe leave them out
> of the series.
Thanks Thierry. I will send v4 accordingly.
> 
> Thierry
> 

      reply	other threads:[~2019-10-09  2:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 16:28 [PATCH v3 0/7] add Tegra194 XUSB host and pad controller support JC Kuo
2019-10-04 16:29 ` [PATCH v3 1/7] xhci: tegra: Parameterize mailbox register addresses JC Kuo
2019-10-04 16:29 ` [PATCH v3 2/7] usb: host: xhci-tegra: Add Tegra194 XHCI support JC Kuo
2019-10-04 16:29 ` [PATCH v3 3/7] phy: tegra: xusb: Protect Tegra186 soc with config JC Kuo
2019-10-04 16:29 ` [PATCH v3 4/7] phy: tegra: xusb: Add Tegra194 support JC Kuo
2019-10-04 16:29 ` [PATCH v3 5/7] dt-bindings: phy: tegra: " JC Kuo
2019-10-04 16:29 ` [PATCH v3 6/7] arm64: tegra: Add XUSB and pad controller on Tegra194 JC Kuo
2019-10-04 16:29 ` [PATCH v3 7/7] arm64: tegra: Enable XUSB host in P2972-0000 board JC Kuo
2019-10-07 11:03 ` [PATCH v3 0/7] add Tegra194 XUSB host and pad controller support Greg KH
2019-10-08 11:29   ` Thierry Reding
2019-10-09  2:23     ` JC Kuo [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=454e29a6-bf31-c75c-0f29-abd18a4ae071@nvidia.com \
    --to=jckuo@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nkristam@nvidia.com \
    --cc=skomatineni@nvidia.com \
    --cc=thierry.reding@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).