linux-kernel - Re: [PATCH v2 0/7] add Tegra194 XUSB host and pad controller support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 5 Oct 2019 00:08:39 +0800
From:   JC Kuo <jckuo@...dia.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     <thierry.reding@...il.com>, <jonathanh@...dia.com>,
        <linux-tegra@...r.kernel.org>, <linux-usb@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <nkristam@...dia.com>, <skomatineni@...dia.com>
Subject: Re: [PATCH v2 0/7] add Tegra194 XUSB host and pad controller support

On 10/4/19 8:23 PM, Greg KH wrote:
> 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 :(
> 
For the first two patches, v2 is identical to v1, sorry that I didn't describe
in patches. For the patches 3 to 7, the individual patch has "Changes in v2:"
session to describe.
I will submit v3 with patch 1 and 2 updated.

Thanks for the guidance,
JC