From: "André Draszik" <andre.draszik@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH v2 0/2] regulator: s2mps11: two small bug fixes (s2mpg1x)
Date: Tue, 10 Feb 2026 17:23:49 +0000 [thread overview]
Message-ID: <20260210-s2mpg1x-regulators-fixes-v2-0-ab3d3457f1ae@linaro.org> (raw)
These two patches fix some code quality / legibility issues in the
newly added s2mpg1x support. Behaviour should not change.
Cheers,
Andre'
Signed-off-by: André Draszik <andre.draszik@linaro.org>
---
Changes in v2:
- update commit message of patch 1, collect tag (Krzysztof)
- Link to v1: https://lore.kernel.org/r/20260209-s2mpg1x-regulators-fixes-v1-0-ead348e64e14@linaro.org
---
André Draszik (2):
regulator: s2mps11: drop redundant sanity checks in s2mpg10_of_parse_cb()
regulator: s2mps11: fix pctrlsel macro usage in s2mpg10_of_parse_cb()
drivers/regulator/s2mps11.c | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)
---
base-commit: 9845cf73f7db6094c0d8419d6adb848028f4a921
change-id: 20260209-s2mpg1x-regulators-fixes-2087fafa2389
Best regards,
--
André Draszik <andre.draszik@linaro.org>
next reply other threads:[~2026-02-10 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 17:23 André Draszik [this message]
2026-02-10 17:23 ` [PATCH v2 1/2] regulator: s2mps11: drop redundant sanity checks in s2mpg10_of_parse_cb() André Draszik
2026-02-10 17:23 ` [PATCH v2 2/2] regulator: s2mps11: fix pctrlsel macro usage " André Draszik
2026-02-17 11:36 ` [PATCH v2 0/2] regulator: s2mps11: two small bug fixes (s2mpg1x) Mark Brown
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=20260210-s2mpg1x-regulators-fixes-v2-0-ab3d3457f1ae@linaro.org \
--to=andre.draszik@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).