From: Johan Hovold <johan@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@kernel.org>,
Justin Chen <justin.chen@broadcom.com>,
Al Cooper <alcooperx@gmail.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 00/11] phy: drop unused module aliases
Date: Thu, 24 Jul 2025 17:48:12 +0200 [thread overview]
Message-ID: <20250724154823.15998-1-johan@kernel.org> (raw)
When fixing up some device leaks in the TI drivers I noticed that the
commits introducing the leaks had also converted the drivers to only
support OF probe.
This series drops the unused platform module alias from the PHY drivers
that never have supported or no longer supports anything but OF probing.
Johan
Johan Hovold (11):
phy: broadcom: brcm-sata: drop unused module alias
phy: broadcom: brcm-usb: drop unused module alias
phy: cadence: Sierra: drop unused module alias
phy: hisilicon: hi6220-usb: drop unused module alias
phy: qualcomm: ipq806x-usb: drop unused module alias
phy: samsung: exynos5-usbdrd: drop unused module alias
phy: samsung: usb2: drop unused module alias
phy: ti: omap-usb2: drop unused module alias
phy: ti: ti-pipe3: drop unused module alias
phy: ti: dm816x-usb: drop unused module alias
phy: ti: omap-control: drop unused module alias
drivers/phy/broadcom/phy-brcm-sata.c | 1 -
drivers/phy/broadcom/phy-brcm-usb.c | 1 -
drivers/phy/cadence/phy-cadence-sierra.c | 1 -
drivers/phy/hisilicon/phy-hi6220-usb.c | 1 -
drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c | 1 -
drivers/phy/samsung/phy-exynos5-usbdrd.c | 1 -
drivers/phy/samsung/phy-samsung-usb2.c | 1 -
drivers/phy/ti/phy-dm816x-usb.c | 1 -
drivers/phy/ti/phy-omap-control.c | 1 -
drivers/phy/ti/phy-omap-usb2.c | 1 -
drivers/phy/ti/phy-ti-pipe3.c | 1 -
11 files changed, 11 deletions(-)
--
2.49.1
next reply other threads:[~2025-07-24 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 15:48 Johan Hovold [this message]
2025-07-24 15:48 ` [PATCH 01/11] phy: broadcom: brcm-sata: drop unused module alias Johan Hovold
2025-07-24 15:48 ` [PATCH 02/11] phy: broadcom: brcm-usb: " Johan Hovold
2025-07-24 15:48 ` [PATCH 03/11] phy: cadence: Sierra: " Johan Hovold
2025-07-24 15:48 ` [PATCH 04/11] phy: hisilicon: hi6220-usb: " Johan Hovold
2025-07-24 15:48 ` [PATCH 05/11] phy: qualcomm: ipq806x-usb: " Johan Hovold
2025-07-24 15:48 ` [PATCH 06/11] phy: samsung: exynos5-usbdrd: " Johan Hovold
2025-07-24 15:48 ` [PATCH 07/11] phy: samsung: usb2: " Johan Hovold
2025-07-24 15:48 ` [PATCH 08/11] phy: ti: omap-usb2: " Johan Hovold
2025-07-24 15:48 ` [PATCH 09/11] phy: ti: ti-pipe3: " Johan Hovold
2025-07-24 15:48 ` [PATCH 10/11] phy: ti: dm816x-usb: " Johan Hovold
2025-07-24 15:48 ` [PATCH 11/11] phy: ti: omap-control: " Johan Hovold
2025-08-06 14:29 ` [PATCH 00/11] phy: drop unused module aliases neil.armstrong
2025-08-06 15:57 ` neil.armstrong
2025-08-12 16:41 ` 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=20250724154823.15998-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=alcooperx@gmail.com \
--cc=justin.chen@broadcom.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=s.nawrocki@samsung.com \
--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
all inboxes | Powered by JetHome®