linux-kernel - Re: [PATCH v12 01/10] dt-bindings: usb: Maxim type-c controller device tree binding document

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]

Message-ID: <20201106104536.GB2785199@kroah.com>
Date:   Fri, 6 Nov 2020 11:45:36 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Badhri Jagan Sridharan <badhri@...gle.com>
Cc:     Rob Herring <robh@...nel.org>, Thierry Reding <treding@...dia.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Prashant Malani <pmalani@...omium.org>,
        Rob Herring <robh+dt@...nel.org>,
        Maxime Ripard <mripard@...nel.org>,
        USB <linux-usb@...r.kernel.org>, Mark Brown <broonie@...nel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Dan Carpenter <dan.carpenter@...cle.com>,
        Guenter Roeck <linux@...ck-us.net>,
        Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH v12 01/10] dt-bindings: usb: Maxim type-c controller
 device tree binding document

On Thu, Oct 29, 2020 at 01:01:52PM -0700, Badhri Jagan Sridharan wrote:
> Hi Rob,
> 
> The error seems to be because the following patch
> 5ed132db5ad4 dt-bindings: connector: Add property to set initial
> current cap for FRS
> is in usb-next but not in the rc1 branch yet. To make the bot
> recognize that this is a
> dependency, Is it suffice to mention the following in the commit description?
> This patch depends on patch "dt-bindings: connector: Add property to
> set initial current cap for FRS".
> Or is there something else that I should do ?

This should all be in linux-next, Rob, is that ok?

thanks,

greg k-h