From: Pascal PAILLET-LME <p.paillet@st.com>
To: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"benjamin.gaignard@linaro.org" <benjamin.gaignard@linaro.org>,
"eballetbo@gmail.com" <eballetbo@gmail.com>,
"axel.lin@ingics.com" <axel.lin@ingics.com>
Cc: Pascal PAILLET-LME <p.paillet@st.com>
Subject: [PATCH v7 7/7] regulator: stpmic1: fix regulator_lock usage
Date: Fri, 30 Nov 2018 09:55:51 +0000 [thread overview]
Message-ID: <1543571742-17995-8-git-send-email-p.paillet@st.com> (raw)
In-Reply-To: <1543571742-17995-1-git-send-email-p.paillet@st.com>
fix a compilation issue due to regulator_lock usage.
Signed-off-by: Pascal Paillet <p.paillet@st.com>
---
changes in v7:
* new patch due to rebase on regul/for-next
drivers/regulator/stpmic1_regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/stpmic1_regulator.c b/drivers/regulator/stpmic1_regulator.c
index eac0848..16ba029 100644
--- a/drivers/regulator/stpmic1_regulator.c
+++ b/drivers/regulator/stpmic1_regulator.c
@@ -489,7 +489,7 @@ static irqreturn_t stpmic1_curlim_irq_handler(int irq, void *data)
{
struct regulator_dev *rdev = (struct regulator_dev *)data;
- regulator_lock(rdev, NULL);
+ regulator_lock(rdev);
/* Send an overcurrent notification */
regulator_notifier_call_chain(rdev,
--
1.9.1
next prev parent reply other threads:[~2018-11-30 9:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 9:55 [PATCH v7 0/7] Introduce STPMIC1 PMIC Driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 1/7] dt-bindings: mfd: document stpmic1 Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 2/7] mfd: stpmic1: add stpmic1 driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 3/7] dt-bindings: input: document stpmic1 pmic onkey Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 4/7] input: stpmic1: add stpmic1 onkey driver Pascal PAILLET-LME
2018-11-30 9:55 ` [PATCH v7 5/7] dt-bindings: watchdog: document stpmic1 pmic watchdog Pascal PAILLET-LME
2018-11-30 9:55 ` Pascal PAILLET-LME [this message]
2018-11-30 9:55 ` [PATCH v7 6/7] watchdog: stpmic1: add stpmic1 watchdog driver Pascal PAILLET-LME
2018-12-03 7:11 ` [PATCH v7 0/7] Introduce STPMIC1 PMIC Driver Lee Jones
2018-12-04 15:24 ` Pascal PAILLET-LME
2018-12-05 9:36 ` Lee Jones
2018-12-05 15:36 ` Pascal PAILLET-LME
2018-12-07 7:31 ` Lee Jones
2018-12-07 12:19 ` Mark Brown
2018-12-14 12:47 ` Lee Jones
2018-12-14 14:36 ` Pascal PAILLET-LME
2019-01-15 0:48 ` dmitry.torokhov
2019-01-16 8:13 ` Lee Jones
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=1543571742-17995-8-git-send-email-p.paillet@st.com \
--to=p.paillet@st.com \
--cc=axel.lin@ingics.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eballetbo@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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 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.