From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-phy@lists.infradead.org>, <linux-arm-msm@vger.kernel.org>,
<andersson@kernel.org>, <vkoul@kernel.org>
Subject: Re: [PATCH -next] phy: qcom: phy-qcom-m31: change m31_ipq5332_regs to static
Date: Thu, 24 Aug 2023 17:03:43 +0530 [thread overview]
Message-ID: <20230824113342.GC15057@varda-linux.qualcomm.com> (raw)
In-Reply-To: <20230824092356.1154839-1-yangyingliang@huawei.com>
On Thu, Aug 24, 2023 at 05:23:56PM +0800, Yang Yingliang wrote:
> m31_ipq5332_regs is only used in phy-qcom-m31.c now, change
> it to static.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/phy/qualcomm/phy-qcom-m31.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/qualcomm/phy-qcom-m31.c b/drivers/phy/qualcomm/phy-qcom-m31.c
> index 99d570f4142a..014278e5428c 100644
> --- a/drivers/phy/qualcomm/phy-qcom-m31.c
> +++ b/drivers/phy/qualcomm/phy-qcom-m31.c
> @@ -82,7 +82,7 @@ struct m31_priv_data {
> unsigned int nregs;
> };
>
> -struct m31_phy_regs m31_ipq5332_regs[] = {
> +static struct m31_phy_regs m31_ipq5332_regs[] = {
> {
> USB_PHY_CFG0,
> UTMI_PHY_OVERRIDE_EN,
Reviewed-by: Varadarajan Narayanan <quic_varada@quicinc.com>
Thanks
Varada
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-phy@lists.infradead.org>, <linux-arm-msm@vger.kernel.org>,
<andersson@kernel.org>, <vkoul@kernel.org>
Subject: Re: [PATCH -next] phy: qcom: phy-qcom-m31: change m31_ipq5332_regs to static
Date: Thu, 24 Aug 2023 17:03:43 +0530 [thread overview]
Message-ID: <20230824113342.GC15057@varda-linux.qualcomm.com> (raw)
In-Reply-To: <20230824092356.1154839-1-yangyingliang@huawei.com>
On Thu, Aug 24, 2023 at 05:23:56PM +0800, Yang Yingliang wrote:
> m31_ipq5332_regs is only used in phy-qcom-m31.c now, change
> it to static.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/phy/qualcomm/phy-qcom-m31.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/qualcomm/phy-qcom-m31.c b/drivers/phy/qualcomm/phy-qcom-m31.c
> index 99d570f4142a..014278e5428c 100644
> --- a/drivers/phy/qualcomm/phy-qcom-m31.c
> +++ b/drivers/phy/qualcomm/phy-qcom-m31.c
> @@ -82,7 +82,7 @@ struct m31_priv_data {
> unsigned int nregs;
> };
>
> -struct m31_phy_regs m31_ipq5332_regs[] = {
> +static struct m31_phy_regs m31_ipq5332_regs[] = {
> {
> USB_PHY_CFG0,
> UTMI_PHY_OVERRIDE_EN,
Reviewed-by: Varadarajan Narayanan <quic_varada@quicinc.com>
Thanks
Varada
> --
> 2.25.1
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-08-24 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 9:23 [PATCH -next] phy: qcom: phy-qcom-m31: change m31_ipq5332_regs to static Yang Yingliang
2023-08-24 9:23 ` Yang Yingliang
2023-08-24 11:33 ` Varadarajan Narayanan [this message]
2023-08-24 11:33 ` Varadarajan Narayanan
2023-09-21 14:26 ` Vinod Koul
2023-09-21 14:26 ` 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=20230824113342.GC15057@varda-linux.qualcomm.com \
--to=quic_varada@quicinc.com \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=vkoul@kernel.org \
--cc=yangyingliang@huawei.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.