From: Doug Anderson <dianders@chromium.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Linux USB List <linux-usb@vger.kernel.org>,
Ravi Chandra Sadineni <ravisadineni@chromium.org>,
Roger Quadros <rogerq@kernel.org>,
Bastien Nocera <hadess@hadess.net>,
Peter Chen <peter.chen@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v24 2/4] dt-bindings: usb: rts5411: Rename property 'companion-hub' to 'peer-hub'
Date: Thu, 30 Jun 2022 16:15:30 -0700 [thread overview]
Message-ID: <CAD=FV=Xj3ejpZ4y3D9gip=rr2jKx9bA1jJWtHVaKv9TYZdQ2BA@mail.gmail.com> (raw)
In-Reply-To: <20220630123445.v24.2.Ie2bbbd3f690826404b8f1059d24edcab33ed898f@changeid>
Hi,
On Thu, Jun 30, 2022 at 12:35 PM Matthias Kaehlcke <mka@chromium.org> wrote:
>
> In the context of USB the term 'companion-hub' is misleading, change the
> name of the property to 'peer-hub'.
>
> There are no upstream users of the 'companion-hub' property, neither in
> the device tree, nor on the driver side, so renaming it shouldn't cause
> any compatibility issues with existing device trees.
>
> Changes in v24:
> - patch added to the series
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> ---
>
> (no changes since v1)
>
> .../devicetree/bindings/usb/realtek,rts5411.yaml | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Matches what Alan said...
Reviewed-by: Douglas Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2022-06-30 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 19:35 [PATCH v24 0/4] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-06-30 19:35 ` [PATCH v24 1/4] of/platform: Add stubs for of_platform_device_create/destroy() Matthias Kaehlcke
2022-06-30 19:35 ` [PATCH v24 2/4] dt-bindings: usb: rts5411: Rename property 'companion-hub' to 'peer-hub' Matthias Kaehlcke
2022-06-30 23:15 ` Doug Anderson [this message]
2022-07-01 20:16 ` Rob Herring
2022-06-30 19:35 ` [PATCH v24 3/4] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-06-30 23:15 ` Doug Anderson
2022-06-30 19:35 ` [PATCH v24 4/4] usb: core: hub: Create platform devices for onboard hubs in hub_probe() Matthias Kaehlcke
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='CAD=FV=Xj3ejpZ4y3D9gip=rr2jKx9bA1jJWtHVaKv9TYZdQ2BA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=michal.simek@xilinx.com \
--cc=mka@chromium.org \
--cc=peter.chen@kernel.org \
--cc=ravisadineni@chromium.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=swboyd@chromium.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).