From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: Rob Herring <robh@kernel.org>,
Thierry Reding <treding@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
Prashant Malani <pmalani@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
USB <linux-usb@vger.kernel.org>, Mark Brown <broonie@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Guenter Roeck <linux@roeck-us.net>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH v12 01/10] dt-bindings: usb: Maxim type-c controller device tree binding document
Date: Fri, 6 Nov 2020 11:45:36 +0100 [thread overview]
Message-ID: <20201106104536.GB2785199@kroah.com> (raw)
In-Reply-To: <CAPTae5L8bnv1S6dK0XkPiF7aha88ed5vfaiw5HAdtvu7TQMD5g@mail.gmail.com>
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
next prev parent reply other threads:[~2020-11-06 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 6:31 [PATCH v12 00/10] TCPM support for FRS and AutoDischarge Disconnect Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 01/10] dt-bindings: usb: Maxim type-c controller device tree binding document Badhri Jagan Sridharan
2020-10-29 15:33 ` Rob Herring
2020-10-29 20:01 ` Badhri Jagan Sridharan
2020-11-06 10:45 ` Greg Kroah-Hartman [this message]
2020-10-29 6:31 ` [PATCH v12 02/10] usb: typec: tcpci_maxim: Fix the compatible string Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 03/10] usb: typec: tcpm: Refactor logic for new-source-frs-typec-current Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 04/10] usb: typec: tcpm: frs sourcing vbus callback Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 05/10] usb: typec: tcpci: " Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 06/10] usb: typec: tcpci_maxim: Fix vbus stuck on upon diconnecting sink Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 07/10] usb: typec: tcpm: Implement enabling Auto Discharge disconnect support Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 08/10] usb: typec: tcpci: Implement Auto discharge disconnect callbacks Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 09/10] usb: typec: tcpci_maxim: Enable auto discharge disconnect Badhri Jagan Sridharan
2020-10-29 6:31 ` [PATCH v12 10/10] usb: typec: tcpci_maxim: Fix uninitialized return variable Badhri Jagan Sridharan
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=20201106104536.GB2785199@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=badhri@google.com \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mripard@kernel.org \
--cc=pmalani@chromium.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=treding@nvidia.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