Linux USB
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Richard Leitner <richard.leitner@linux.dev>
Cc: "Neumann, Bastian" <Bastian.Neumann@dentsplysirona.com>,
	Tommaso Merciai <tomm.merciai@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Richard Leitner <richard.leitner@skidata.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: usb: USB2512x boost value for up- and downstream ports
Date: Mon, 14 Mar 2022 09:38:47 -0600	[thread overview]
Message-ID: <Yi9hhyYqbnAOgc7u@robh.at.kernel.org> (raw)
In-Reply-To: <Yi5NYJfyvYcC9X+j@ltleri2>

On Sun, Mar 13, 2022 at 09:00:32PM +0100, Richard Leitner wrote:
> On Fri, Mar 11, 2022 at 08:48:17AM -0600, Rob Herring wrote:
> > On Fri, Mar 11, 2022 at 12:09:42PM +0000, Neumann, Bastian wrote:
> > > This patch adds devicetree documentation for signal boosting properties.
> > > 
> > > Signed-off-by: Bastian Neumann <bastian.neumann@dentsplysirona.com>
> > > ---
> > >  .../devicetree/bindings/usb/usb251xb.txt      | 22 +++++++++++++++++++
> > >  1 file changed, 22 insertions(+)
> > 
> > A popular feature all the sudden. Which one are we supposed to apply? 
> > This one or this[1]?
> 
> This seems to be a superset of the previous patchset from Tommaso.
> Therefore I'd definitley vote for this one if a v2 of it [2] gets
> merged (it was declined by GregKH because of the e-mail signature and
> fomatting issues).
> 
> Until then I assume [1] should be applied as it represents the current
> master state due to
> commit 5c2b9c61ae5d (usb: usb251xb: add boost-up property support, 2022-01-28)
> being already merged.

No, because there are changes requested on [1]. And I guess fixes will 
be needed to the driver too if it already got picked up.

Rob

      reply	other threads:[~2022-03-14 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 12:09 [PATCH 2/2] dt-bindings: usb: USB2512x boost value for up- and downstream ports Neumann, Bastian
2022-03-11 13:07 ` Krzysztof Kozlowski
2022-03-11 14:48 ` Rob Herring
2022-03-13 20:00   ` Richard Leitner
2022-03-14 15:38     ` Rob Herring [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=Yi9hhyYqbnAOgc7u@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Bastian.Neumann@dentsplysirona.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=richard.leitner@linux.dev \
    --cc=richard.leitner@skidata.com \
    --cc=tomm.merciai@gmail.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