From: Vinod Koul <vkoul@kernel.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: jckuo@nvidia.com, kishon@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-phy@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] phy: tegra: xusb: Add missing tegra_xusb_port_unregister for usb2_port and ulpi_port
Date: Wed, 12 Apr 2023 21:51:54 +0530 [thread overview]
Message-ID: <ZDbaos9E77CAyisG@matsya> (raw)
In-Reply-To: <20221129111634.1547747-1-cuigaosheng1@huawei.com>
On 29-11-22, 19:16, Gaosheng Cui wrote:
> The tegra_xusb_port_unregister should be called when usb2_port
> and ulpi_port map fails in tegra_xusb_add_usb2_port() or in
> tegra_xusb_add_ulpi_port(), fix it.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: jckuo@nvidia.com, kishon@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-phy@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] phy: tegra: xusb: Add missing tegra_xusb_port_unregister for usb2_port and ulpi_port
Date: Wed, 12 Apr 2023 21:51:54 +0530 [thread overview]
Message-ID: <ZDbaos9E77CAyisG@matsya> (raw)
In-Reply-To: <20221129111634.1547747-1-cuigaosheng1@huawei.com>
On 29-11-22, 19:16, Gaosheng Cui wrote:
> The tegra_xusb_port_unregister should be called when usb2_port
> and ulpi_port map fails in tegra_xusb_add_usb2_port() or in
> tegra_xusb_add_ulpi_port(), fix it.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2023-04-12 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 11:16 [PATCH] phy: tegra: xusb: Add missing tegra_xusb_port_unregister for usb2_port and ulpi_port Gaosheng Cui
2022-11-29 11:16 ` Gaosheng Cui
2023-04-05 12:35 ` Thierry Reding
2023-04-05 12:35 ` Thierry Reding
2023-04-12 16:21 ` Vinod Koul [this message]
2023-04-12 16:21 ` Vinod Koul
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=ZDbaos9E77CAyisG@matsya \
--to=vkoul@kernel.org \
--cc=cuigaosheng1@huawei.com \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.