From: Patrice Chotard <patrice.chotard@st.com>
To: Axel Lin <axel.lin@ingics.com>, Kishon Vijay Abraham I <kishon@ti.com>
Cc: Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
Maxime Coquelin <maxime.coquelin@st.com>,
Heiko Stuebner <heiko@sntech.de>,
Kamil Debski <k.debski@samsung.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: Constify struct phy_ops variables
Date: Wed, 15 Jul 2015 09:47:24 +0200 [thread overview]
Message-ID: <55A6100C.9000509@st.com> (raw)
In-Reply-To: <1436945631.10834.1.camel@ingics.com>
Hi Axel
On 07/15/2015 09:33 AM, Axel Lin wrote:
> The phy_ops variables are never modified after initialized in these
> drivers, so make them const.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Note, the change for drivers/phy/phy-tusb1210.c depends on
> my previous patch "[PATCH] phy: ulpi_phy: Add const qualifier to ops".
>
> drivers/phy/phy-armada375-usb2.c | 2 +-
> drivers/phy/phy-bcm-kona-usb2.c | 2 +-
> drivers/phy/phy-berlin-sata.c | 2 +-
> drivers/phy/phy-berlin-usb.c | 2 +-
> drivers/phy/phy-brcmstb-sata.c | 2 +-
> drivers/phy/phy-dm816x-usb.c | 2 +-
> drivers/phy/phy-exynos-dp-video.c | 2 +-
> drivers/phy/phy-exynos-mipi-video.c | 2 +-
> drivers/phy/phy-exynos5-usbdrd.c | 2 +-
> drivers/phy/phy-exynos5250-sata.c | 2 +-
> drivers/phy/phy-hix5hd2-sata.c | 2 +-
> drivers/phy/phy-miphy28lp.c | 2 +-
> drivers/phy/phy-miphy365x.c | 2 +-
> drivers/phy/phy-mvebu-sata.c | 2 +-
> drivers/phy/phy-omap-usb2.c | 2 +-
> drivers/phy/phy-qcom-apq8064-sata.c | 2 +-
> drivers/phy/phy-qcom-ipq806x-sata.c | 2 +-
> drivers/phy/phy-qcom-ufs-i.h | 2 +-
> drivers/phy/phy-qcom-ufs-qmp-14nm.c | 2 +-
> drivers/phy/phy-qcom-ufs-qmp-20nm.c | 2 +-
> drivers/phy/phy-qcom-ufs.c | 2 +-
> drivers/phy/phy-rcar-gen2.c | 2 +-
> drivers/phy/phy-rockchip-usb.c | 2 +-
> drivers/phy/phy-samsung-usb2.c | 2 +-
> drivers/phy/phy-spear1310-miphy.c | 2 +-
> drivers/phy/phy-spear1340-miphy.c | 2 +-
> drivers/phy/phy-stih41x-usb.c | 2 +-
> drivers/phy/phy-sun4i-usb.c | 2 +-
> drivers/phy/phy-sun9i-usb.c | 2 +-
> drivers/phy/phy-ti-pipe3.c | 2 +-
> drivers/phy/phy-tusb1210.c | 2 +-
> 31 files changed, 31 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/phy/phy-armada375-usb2.c b/drivers/phy/phy-armada375-usb2.c
> index 8ccc395..a3f1e73 100644
> --- a/drivers/phy/phy-armada375-usb2.c
> +++ b/drivers/phy/phy-armada375-usb2.c
> @@ -51,7 +51,7 @@ static int armada375_usb_phy_init(struct phy *phy)
> return 0;
> }
>
[snip]
>
> -static struct phy_ops phy_ops = {
> +static const struct phy_ops phy_ops = {
> .power_on = tusb1210_power_on,
> .power_off = tusb1210_power_off,
> .owner = THIS_MODULE,
for
drivers/phy/phy-miphy28lp.c,
drivers/phy/phy-miphy365x.c and
drivers/phy/phy-stih41x-usb.c
Acked-by: Patrice Chotard <patrice.chotard@st.com>
Thanks
prev parent reply other threads:[~2015-07-15 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 7:33 [PATCH] phy: Constify struct phy_ops variables Axel Lin
2015-07-15 7:47 ` Patrice Chotard [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=55A6100C.9000509@st.com \
--to=patrice.chotard@st.com \
--cc=axel.lin@ingics.com \
--cc=heiko@sntech.de \
--cc=k.debski@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=maxime.ripard@free-electrons.com \
--cc=srinivas.kandagatla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox