linux-kernel - Applied "regulator: stpmic1: fix regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20181203120720.31E86440080@finisterre.ee.mobilebroadband>
Date:   Mon,  3 Dec 2018 12:07:20 +0000 (GMT)
From:   Mark Brown <broonie@...nel.org>
To:     Pascal PAILLET-LME <p.paillet@...com>
Cc:     Pascal Paillet <p.paillet@...com>, Mark Brown <broonie@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Applied "regulator: stpmic1: fix regulator_lock usage" to the regulator tree

The patch

   regulator: stpmic1: fix regulator_lock usage

has been applied to the regulator tree at

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git 

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.  

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

>From db6e6244cb714029959f26caa58522e3c20d4c61 Mon Sep 17 00:00:00 2001
From: Pascal PAILLET-LME <p.paillet@...com>
Date: Fri, 30 Nov 2018 09:55:51 +0000
Subject: [PATCH] regulator: stpmic1: fix regulator_lock usage

fix a compilation issue due to regulator_lock usage.

Signed-off-by: Pascal Paillet <p.paillet@...com>
Signed-off-by: Mark Brown <broonie@...nel.org>
---
 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 eac0848a78c7..16ba0297f709 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,
-- 
2.20.0.rc1