From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: usb: generic-ohci: Add missing compatible strings
Date: Thu, 4 Feb 2021 00:50:01 +0100 [thread overview]
Message-ID: <YBs2qcfSKfeBHBlr@kroah.com> (raw)
In-Reply-To: <20210203210834.GD3706951@robh.at.kernel.org>
On Wed, Feb 03, 2021 at 03:08:34PM -0600, Rob Herring wrote:
> On Wed, Feb 03, 2021 at 10:07:47AM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Feb 02, 2021 at 11:54:39AM -0600, Rob Herring wrote:
> > > The generic OHCI binding needs to document all the specific compatible
> > > strings so we can track undocumented compatible strings. Add all the
> > > compatible strings from in tree users.
> > >
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: linux-usb@vger.kernel.org
> > > Signed-off-by: Rob Herring <robh@kernel.org>
> > > ---
> > > .../devicetree/bindings/usb/generic-ohci.yaml | 34 +++++++++++++++++--
> > > 1 file changed, 32 insertions(+), 2 deletions(-)
> >
> > Both look fine to me, do you want me to take this through my trees or
> > will you take them?
>
> You'd better take them. I don't think they conflict with any of the
> other USB binding changes, but there have been a few this cycle IIRC.
Ok, now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-02-03 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 17:54 [PATCH 1/2] dt-bindings: usb: generic-ehci: Add missing compatible strings Rob Herring
2021-02-02 17:54 ` [PATCH 2/2] dt-bindings: usb: generic-ohci: " Rob Herring
2021-02-03 9:07 ` Greg Kroah-Hartman
2021-02-03 21:08 ` Rob Herring
2021-02-03 23:50 ` Greg Kroah-Hartman [this message]
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=YBs2qcfSKfeBHBlr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).