From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stanley Chang <stanley_chang@realtek.com>
Cc: kernel test robot <lkp@intel.com>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Bagas Sanjaya <bagasdotme@gmail.com>, Ray Chi <raychi@google.com>,
Douglas Anderson <dianders@chromium.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Flavio Suligoi <f.suligoi@asem.it>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 2/3] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0/3.0 PHY
Date: Mon, 29 May 2023 15:25:33 +0100 [thread overview]
Message-ID: <2023052915-repurpose-partner-20a8@gregkh> (raw)
In-Reply-To: <20230525022617.30537-2-stanley_chang@realtek.com>
On Thu, May 25, 2023 at 10:26:03AM +0800, Stanley Chang wrote:
> Realtek DHC (digital home center) RTD SoCs support DWC3 XHCI USB 2.0/3.0
> controller. Added two drivers to drive the USB 2.0/3.0 PHY transceivers.
> For USB 3.0 transceivers, a driver phy-rtk-usb3 is provided.
> The driver phy-rtk-usb2 is used to support USB 2.0 transceivers.
>
> Signed-off-by: Stanley Chang <stanley_chang@realtek.com>
> Reported-by: kernel test robot <lkp@intel.com>
The kernel test robot did not report that a new driver was needed :(
next prev parent reply other threads:[~2023-05-29 14:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 2:26 [PATCH v2 1/3] usb: phy: add usb phy notify port status API Stanley Chang
2023-05-25 2:26 ` [PATCH v2 2/3] phy: realtek: usb: Add driver for the Realtek SoC USB 2.0/3.0 PHY Stanley Chang
2023-05-29 14:25 ` Greg Kroah-Hartman [this message]
2023-05-30 1:50 ` Stanley Chang[昌育德]
2023-05-30 7:31 ` Greg Kroah-Hartman
2023-05-30 7:37 ` Stanley Chang[昌育德]
2023-05-25 2:26 ` [PATCH v2 3/3] dt-bindings: phy: realtek: Add the doc about " Stanley Chang
2023-05-29 18:59 ` Conor Dooley
2023-05-30 3:08 ` Stanley Chang[昌育德]
2023-05-30 6:56 ` Conor Dooley
[not found] ` <202305310146.34V1kevI7026106@rtits1.realtek.com.tw>
2023-06-01 2:24 ` Stanley Chang[昌育德]
2023-06-01 20:13 ` Conor Dooley
[not found] ` <0b2143ca-ead7-c8fa-2e80-a94222af51ca@linaro.org>
2023-06-01 10:49 ` Stanley Chang[昌育德]
2023-06-01 15:32 ` Krzysztof Kozlowski
2023-06-02 3:20 ` Stanley Chang[昌育德]
2023-06-02 7:10 ` Krzysztof Kozlowski
2023-06-02 7:33 ` Stanley Chang[昌育德]
2023-05-29 14:27 ` [PATCH v2 1/3] usb: phy: add usb phy notify port status API Greg Kroah-Hartman
2023-05-30 2:19 ` Stanley Chang[昌育德]
2023-05-30 7:32 ` Greg Kroah-Hartman
2023-05-30 7:38 ` Stanley Chang[昌育德]
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=2023052915-repurpose-partner-20a8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=f.suligoi@asem.it \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=m.grzeschik@pengutronix.de \
--cc=mathias.nyman@linux.intel.com \
--cc=raychi@google.com \
--cc=robh+dt@kernel.org \
--cc=stanley_chang@realtek.com \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@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).