From: "Thierry Reding" <thierry.reding@gmail.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Chun-Kuang Hu" <chunkuang.hu@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
<linux-phy@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-sunxi@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-amlogic@lists.infradead.org>, <netdev@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-renesas-soc@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-tegra@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] phy: constify of_phandle_args in xlate
Date: Mon, 19 Feb 2024 16:58:25 +0100 [thread overview]
Message-ID: <CZ96H72GI4Z0.SZJBZXA1VXJZ@gmail.com> (raw)
In-Reply-To: <20240217093937.58234-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 3381 bytes --]
On Sat Feb 17, 2024 at 10:39 AM CET, Krzysztof Kozlowski wrote:
> The xlate callbacks are supposed to translate of_phandle_args to proper
> provider without modifying the of_phandle_args. Make the argument
> pointer to const for code safety and readability.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> drivers/phy/allwinner/phy-sun4i-usb.c | 2 +-
> drivers/phy/amlogic/phy-meson-g12a-usb3-pcie.c | 2 +-
> drivers/phy/broadcom/phy-bcm-sr-pcie.c | 2 +-
> drivers/phy/broadcom/phy-bcm-sr-usb.c | 2 +-
> drivers/phy/broadcom/phy-bcm63xx-usbh.c | 2 +-
> drivers/phy/broadcom/phy-brcm-usb.c | 2 +-
> drivers/phy/freescale/phy-fsl-imx8qm-lvds-phy.c | 2 +-
> drivers/phy/freescale/phy-fsl-lynx-28g.c | 2 +-
> drivers/phy/hisilicon/phy-histb-combphy.c | 2 +-
> drivers/phy/intel/phy-intel-lgm-combo.c | 2 +-
> drivers/phy/lantiq/phy-lantiq-vrx200-pcie.c | 2 +-
> drivers/phy/marvell/phy-armada375-usb2.c | 2 +-
> drivers/phy/marvell/phy-armada38x-comphy.c | 2 +-
> drivers/phy/marvell/phy-berlin-sata.c | 2 +-
> drivers/phy/marvell/phy-mvebu-a3700-comphy.c | 2 +-
> drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 2 +-
> drivers/phy/mediatek/phy-mtk-mipi-csi-0-5.c | 2 +-
> drivers/phy/mediatek/phy-mtk-tphy.c | 2 +-
> drivers/phy/mediatek/phy-mtk-xsphy.c | 2 +-
> drivers/phy/microchip/lan966x_serdes.c | 2 +-
> drivers/phy/microchip/sparx5_serdes.c | 2 +-
> drivers/phy/mscc/phy-ocelot-serdes.c | 2 +-
> drivers/phy/phy-core.c | 8 ++++----
> drivers/phy/phy-xgene.c | 2 +-
> drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 2 +-
> drivers/phy/ralink/phy-mt7621-pci.c | 2 +-
> drivers/phy/renesas/phy-rcar-gen2.c | 2 +-
> drivers/phy/renesas/phy-rcar-gen3-usb2.c | 2 +-
> drivers/phy/renesas/r8a779f0-ether-serdes.c | 2 +-
> drivers/phy/rockchip/phy-rockchip-naneng-combphy.c | 2 +-
> drivers/phy/rockchip/phy-rockchip-pcie.c | 2 +-
> drivers/phy/samsung/phy-exynos-mipi-video.c | 2 +-
> drivers/phy/samsung/phy-exynos5-usbdrd.c | 2 +-
> drivers/phy/samsung/phy-samsung-usb2.c | 2 +-
> drivers/phy/socionext/phy-uniphier-usb2.c | 2 +-
> drivers/phy/st/phy-miphy28lp.c | 2 +-
> drivers/phy/st/phy-spear1310-miphy.c | 2 +-
> drivers/phy/st/phy-spear1340-miphy.c | 2 +-
> drivers/phy/st/phy-stm32-usbphyc.c | 2 +-
> drivers/phy/tegra/xusb.c | 2 +-
> drivers/phy/ti/phy-am654-serdes.c | 2 +-
> drivers/phy/ti/phy-da8xx-usb.c | 2 +-
> drivers/phy/ti/phy-gmii-sel.c | 2 +-
> drivers/phy/xilinx/phy-zynqmp.c | 2 +-
> drivers/pinctrl/tegra/pinctrl-tegra-xusb.c | 2 +-
> include/linux/phy/phy.h | 14 +++++++-------
> 46 files changed, 55 insertions(+), 55 deletions(-)
Makes sense:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-19 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 9:39 [PATCH] phy: constify of_phandle_args in xlate Krzysztof Kozlowski
2024-02-19 15:58 ` Thierry Reding [this message]
2024-02-21 22:07 ` Linus Walleij
2024-02-21 22:12 ` Florian Fainelli
2024-02-23 12:15 ` 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=CZ96H72GI4Z0.SZJBZXA1VXJZ@gmail.com \
--to=thierry.reding@gmail.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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).