From: kbuild test robot <lkp@intel.com>
To: Sivaprakash Murugesan <sivaprak@codeaurora.org>
Cc: kbuild-all@lists.01.org, agross@kernel.org,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH] clk: qcom: apss_pll_offsets[] can be static
Date: Fri, 28 Feb 2020 01:40:04 +0800 [thread overview]
Message-ID: <20200227174004.GA29216@f6f0d943a460> (raw)
In-Reply-To: <1582797318-26288-3-git-send-email-sivaprak@codeaurora.org>
Fixes: bfce07143090 ("clk: qcom: Add ipq6018 apss clock controller")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
apss-ipq6018.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/qcom/apss-ipq6018.c b/drivers/clk/qcom/apss-ipq6018.c
index 04b8962dbc8e0..663f0949ab109 100644
--- a/drivers/clk/qcom/apss-ipq6018.c
+++ b/drivers/clk/qcom/apss-ipq6018.c
@@ -36,7 +36,7 @@ enum {
P_APSS_PLL
};
-const u8 apss_pll_offsets[] = {
+static const u8 apss_pll_offsets[] = {
[PLL_OFF_L_VAL] = 0x08,
[PLL_OFF_ALPHA_VAL] = 0x10,
[PLL_OFF_USER_CTL] = 0x18,
next prev parent reply other threads:[~2020-02-28 1:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 9:55 [PATCH 0/2] Add APSS clock controller support for IPQ6018 Sivaprakash Murugesan
2020-02-27 9:55 ` [PATCH 1/2] clk: qcom: Add DT bindings for ipq6018 apss clock controller Sivaprakash Murugesan
2020-02-27 10:38 ` Sibi Sankar
2020-02-27 10:55 ` Sivaprakash Murugesan
2020-04-05 8:19 ` Sivaprakash Murugesan
2020-02-27 17:14 ` Rob Herring
2020-03-04 5:24 ` Sivaprakash Murugesan
2020-03-09 21:07 ` Rob Herring
2020-03-09 21:13 ` Rob Herring
2020-04-05 8:30 ` Sivaprakash Murugesan
2020-02-27 9:55 ` [PATCH 2/2] clk: qcom: Add " Sivaprakash Murugesan
2020-02-27 17:40 ` kbuild test robot
2020-02-27 17:40 ` kbuild test robot [this message]
2020-03-09 20:24 ` Stephen Boyd
2020-04-05 8:26 ` Sivaprakash Murugesan
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=20200227174004.GA29216@f6f0d943a460 \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@codeaurora.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).