From: Vinod Koul <vkoul@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: devicetree@vger.kernel.org, fushi.peng@nxp.com,
imx@lists.linux.dev, kernel@pengutronix.de, kishon@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
robh+dt@kernel.org, s.hauer@pengutronix.de, shawnguo@kernel.org
Subject: Re: [PATCH v5 0/6] phy: cadence: salvo: some fixes and workarounds
Date: Fri, 19 May 2023 23:14:23 +0530 [thread overview]
Message-ID: <ZGe1d/8tGGl+rTNa@matsya> (raw)
In-Reply-To: <20230517161646.3418250-1-Frank.Li@nxp.com>
On 17-05-23, 12:16, Frank Li wrote:
>
> Sorry I have not realized some patches were missed at upstream kernel.
> Version number continue with previous
> https://lore.kernel.org/imx/ZGOCT0Mdg3Jtar6c@matsya/T/#t
>
> Peter's Fixes:
> - Bist issue
> - fix corrupt package from devices when start transferring less than 20us
> - fix the FSM in controller seeing the disconnection at L1 use case.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2023-05-19 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:16 [PATCH v5 0/6] phy: cadence: salvo: some fixes and workarounds Frank Li
2023-05-17 16:16 ` [PATCH v5 1/6] phy: cadence: salvo: add access for USB2PHY Frank Li
2023-05-17 16:16 ` [PATCH v5 2/6] phy: cadence: salvo: decrease delay value to zero for txvalid Frank Li
2023-05-17 16:16 ` [PATCH v5 3/6] phy: cadence: salvo: add bist fix Frank Li
2023-05-17 16:16 ` [PATCH v5 4/6] phy: cadence: salvo: add .set_mode API Frank Li
2023-05-17 16:16 ` [PATCH v5 5/6] phy: cadence: salvo: Add cdns,usb2-disconnect-threshold-microvolt property Frank Li
2023-05-17 16:16 ` [PATCH v5 6/6] dt-bindings: phy: cdns,salvo: add property cdns,usb2-disconnect-threshold-microvolt Frank Li
2023-05-19 17:44 ` Vinod Koul [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=ZGe1d/8tGGl+rTNa@matsya \
--to=vkoul@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fushi.peng@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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