linux-kernel - Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 12 Oct 2017 14:01:41 +0200
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Felipe Balbi <felipe.balbi@...ux.intel.com>,
        Amelie DELAUNAY <amelie.delaunay@...com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Russell King <linux@...linux.org.uk>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        John Youn <johnyoun@...opsys.com>
CC:     "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Benjamin GAIGNARD <benjamin.gaignard@...com>
Subject: Re: [PATCHv2 0/7] Add support for USB OTG on STM32F7



On 10/12/2017 01:53 PM, Felipe Balbi wrote:
> 
> Hi,
> 
> Felipe Balbi <felipe.balbi@...ux.intel.com> writes:
>>>>> I thought that patches 1 and 2, as they are "driver" patches, had to be
>>>>> applied on USB tree (so Felipe's one), and the others (3 to 7) had to be
>>>>> applied on STM32-DT tree (Alex's one). Did I miss something?
>>>>
>>>> patch 1 is documentation, right? Without the documentation patch,
>>>> checkpatch will cringe :-) So either way works.
>>>>
>>>> If you insist, I can take 1-2 through my tree. No worries.
>>>
>>> I don't want to insist :) but for me it is better (and more safe) if you
>>> take patch 1&2 in your tree, and will take others in mine.
>>
>> Okay, I'll apply 1&2
> 
> they are now in my testing/next and next branches.

Thanks Felipe
>