From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
gabriel.fernandez@st.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
gabriel.fernandez.st@gmail.com,
Loic PALLARDY <loic.pallardy@st.com>,
benjamin GAIGNARD <benjamin.gaignard@st.com>,
Michael Turquette <mturquette@baylibre.com>,
sboyd@kernel.org
Subject: [RFC PATCH] reset: stm32mp1: stm32_reset_ops can be static
Date: Fri, 16 Mar 2018 20:22:33 +0800 [thread overview]
Message-ID: <20180316122233.GA85610@lkp-sb05> (raw)
In-Reply-To: <1521045001-30788-3-git-send-email-gabriel.fernandez@st.com>
Fixes: d05c83341cbc ("reset: stm32mp1: Enable stm32mp1 reset driver")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
reset-stm32mp1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/reset/reset-stm32mp1.c b/drivers/reset/reset-stm32mp1.c
index 5e25388..ed44604 100644
--- a/drivers/reset/reset-stm32mp1.c
+++ b/drivers/reset/reset-stm32mp1.c
@@ -70,7 +70,7 @@ static int stm32_reset_status(struct reset_controller_dev *rcdev,
return !(reg & BIT(offset));
}
-const struct reset_control_ops stm32_reset_ops = {
+static const struct reset_control_ops stm32_reset_ops = {
.assert = stm32_reset_assert,
.deassert = stm32_reset_deassert,
.status = stm32_reset_status,
next prev parent reply other threads:[~2018-03-16 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 16:29 [PATCH v2 0/2] Introduce STM32MP1 Reset driver gabriel.fernandez
2018-03-14 16:30 ` [PATCH v2 1/2] dt-bindings: reset: add STM32MP1 resets gabriel.fernandez
2018-03-18 12:49 ` Rob Herring
2018-03-14 16:30 ` [PATCH v2 2/2] reset: stm32mp1: Enable stm32mp1 reset driver gabriel.fernandez
2018-03-16 12:22 ` kbuild test robot [this message]
2018-03-16 12:22 ` kbuild test robot
2018-03-16 13:29 ` Philipp Zabel
2018-03-16 14:35 ` Gabriel FERNANDEZ
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=20180316122233.GA85610@lkp-sb05 \
--to=lkp@intel.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez.st@gmail.com \
--cc=gabriel.fernandez@st.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).