From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, piyush.mehta@amd.com, michal.simek@amd.com,
francesco.dolcini@toradex.com, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Eichenberger <stefan.eichenberger@toradex.com>
Subject: Re: [PATCH] dt-bindings: usb: microchip,usb5744: Remove peer-hub as requirement
Date: Fri, 9 Feb 2024 09:40:48 +0000 [thread overview]
Message-ID: <2024020941-small-devious-1e36@gregkh> (raw)
In-Reply-To: <ZcXfflAvkzHzWBfb@eichest-laptop>
On Fri, Feb 09, 2024 at 09:17:02AM +0100, Stefan Eichenberger wrote:
> Hi Greg,
>
> On Tue, Jan 30, 2024 at 08:35:05AM +0100, Stefan Eichenberger wrote:
> > From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> >
> > The peer-hub is used to model the relationship between the USB 2 and USB
> > 3 hub. However, it is possible to only connect USB 2 without having
> > USB 3. Therefore, the peer-hub property should not be marked as required.
>
> I just wanted to ask if everything is okay with the patch and if its
> fine to apply it or if it needs some updates?
That was only 10 days ago, please give us a chance to catch up on
reviews.
In the meantime, while waiting, please review other changes on the
lists, that way yours moves higher up in the queue. Any reason why you
can't do that now?
thanks,
greg k-h
prev parent reply other threads:[~2024-02-09 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 7:35 [PATCH] dt-bindings: usb: microchip,usb5744: Remove peer-hub as requirement Stefan Eichenberger
2024-01-30 8:50 ` Francesco Dolcini
2024-01-30 11:01 ` Michal Simek
2024-01-30 17:58 ` Conor Dooley
2024-02-09 8:17 ` Stefan Eichenberger
2024-02-09 9:40 ` Greg KH [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=2024020941-small-devious-1e36@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eichest@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=piyush.mehta@amd.com \
--cc=robh+dt@kernel.org \
--cc=stefan.eichenberger@toradex.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;
as well as URLs for NNTP newsgroup(s).