From: Greg KH <gregkh@linuxfoundation.org>
To: JC Kuo <jckuo@nvidia.com>
Cc: thierry.reding@gmail.com, 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 v2 0/7] add Tegra194 XUSB host and pad controller support
Date: Fri, 4 Oct 2019 14:23:22 +0200 [thread overview]
Message-ID: <20191004122322.GB422178@kroah.com> (raw)
In-Reply-To: <20191004081941.4831-1-jckuo@nvidia.com>
On Fri, Oct 04, 2019 at 04:19:34PM +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.
>
> JC Kuo (7):
> xhci: tegra: Parameterize mailbox register addresses
> usb: host: xhci-tegra: Add Tegra194 XHCI support
> phy: tegra: xusb: Protect Tegra186 soc with config
> phy: tegra: xusb: Add Tegra194 support
> dt-bindings: phy: tegra: Add Tegra194 support
> arm64: tegra: Add XUSB and pad controller on Tegra194
> arm64: tegra: Enable XUSB host in P2972-0000 board
What changed from v1? You need to put that somewhere, usually in the
patches themselves, below the --- line.
Or at the very least, in the cover letter.
Given that I can't find it anywhere here, I'll expect a v3 with that
information to be sent soon :(
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-04 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 8:19 [PATCH v2 0/7] add Tegra194 XUSB host and pad controller support JC Kuo
2019-10-04 8:19 ` [PATCH v2 1/7] xhci: tegra: Parameterize mailbox register addresses JC Kuo
2019-10-04 8:19 ` [PATCH v2 2/7] usb: host: xhci-tegra: Add Tegra194 XHCI support JC Kuo
2019-10-04 8:19 ` [PATCH v2 3/7] phy: tegra: xusb: Protect Tegra186 soc with config JC Kuo
2019-10-04 8:19 ` [PATCH v2 4/7] phy: tegra: xusb: Add Tegra194 support JC Kuo
2019-10-04 8:19 ` [PATCH v2 5/7] dt-bindings: phy: tegra: " JC Kuo
2019-10-04 8:19 ` [PATCH v2 6/7] arm64: tegra: Add XUSB and pad controller on Tegra194 JC Kuo
2019-10-04 8:19 ` [PATCH v2 7/7] arm64: tegra: Enable XUSB host in P2972-0000 board JC Kuo
2019-10-04 12:23 ` Greg KH [this message]
2019-10-04 16:08 ` [PATCH v2 0/7] add Tegra194 XUSB host and pad controller support JC Kuo
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=20191004122322.GB422178@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=jckuo@nvidia.com \
--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