From: Antonio Borneo <antonio.borneo@foss.st.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Bartosz Golaszewski <brgl@bgdev.pl>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Cc: Antonio Borneo <antonio.borneo@foss.st.com>,
Christophe Roullier <christophe.roullier@foss.st.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
Valentin Caron <valentin.caron@foss.st.com>
Subject: [PATCH v2 6/9] pinctrl: stm32: Avoid keeping a bool value in a u32 variable
Date: Fri, 5 Sep 2025 15:55:44 +0200 [thread overview]
Message-ID: <20250905135547.934729-7-antonio.borneo@foss.st.com> (raw)
In-Reply-To: <20250905135547.934729-1-antonio.borneo@foss.st.com>
Change type of variable to avoid keeping the bool return value in
a variable of u32 type.
Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
---
drivers/pinctrl/stm32/pinctrl-stm32.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c b/drivers/pinctrl/stm32/pinctrl-stm32.c
index 76555d18720f6..8d2f409342313 100644
--- a/drivers/pinctrl/stm32/pinctrl-stm32.c
+++ b/drivers/pinctrl/stm32/pinctrl-stm32.c
@@ -1148,7 +1148,7 @@ static u32 stm32_pconf_get_bias(struct stm32_gpio_bank *bank,
static bool stm32_pconf_get(struct stm32_gpio_bank *bank,
unsigned int offset, bool dir)
{
- u32 val;
+ bool val;
if (dir)
val = !!(readl_relaxed(bank->base + STM32_GPIO_IDR) &
--
2.34.1
next prev parent reply other threads:[~2025-09-05 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 13:55 [PATCH v2 0/9] pinctrl: stm32: Support I/O synchronization Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 1/9] pinctrl: pinconf-generic: Add property "skew-delay-direction" Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 2/9] dt-bindings: pincfg-node: " Antonio Borneo
2025-09-10 2:08 ` Rob Herring (Arm)
2025-09-30 12:23 ` Linus Walleij
2025-10-01 14:36 ` Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 3/9] pinctrl: stm32: Rework stm32_pconf_parse_conf() Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 4/9] pinctrl: stm32: Simplify handling of backup pin status Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 5/9] pinctrl: stm32: Drop useless spinlock save and restore Antonio Borneo
2025-09-05 13:55 ` Antonio Borneo [this message]
2025-09-05 13:55 ` [PATCH v2 7/9] pinctrl: stm32: Support I/O synchronization parameters Antonio Borneo
2025-09-05 13:55 ` [PATCH v2 8/9] dt-bindings: " Antonio Borneo
2025-09-10 2:10 ` Rob Herring (Arm)
2025-09-05 13:55 ` [PATCH v2 9/9] arm64: dts: st: Add I/O sync to eth2 pinctrl in stm32mp25-pinctrl.dtsi Antonio Borneo
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=20250905135547.934729-7-antonio.borneo@foss.st.com \
--to=antonio.borneo@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=brgl@bgdev.pl \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=valentin.caron@foss.st.com \
/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
all inboxes | Powered by JetHome®