From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: linus.walleij@linaro.org, lokeshvutla@ti.com, nm@ti.com,
robh@kernel.org, tony@atomide.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/3] pinctrl: ti: ti-iodelay: Fix some error handling paths + 2 unrelated clean-ups
Date: Tue, 9 Jul 2024 22:37:42 +0200 [thread overview]
Message-ID: <cover.1720556038.git.christophe.jaillet@wanadoo.fr> (raw)
The first patch is completly speculative. It is based on static analysis
when a function is called in the remove() function, but not in the
error handling path of the probe.
When looking deeper at it, it seems that part of
ti_iodelay_pinconf_init_dev() also needed to be fixed.
/!\ This is completly speculative. So review with care /!\
Patch 2 and 3 are just constification patches spoted while looking at
the code.
Christophe JAILLET (3):
pinctrl: ti: ti-iodelay: Fix some error handling paths
pinctrl: ti: ti-iodelay: Constify struct ti_iodelay_reg_data
pinctrl: ti: ti-iodelay: Constify struct regmap_config
drivers/pinctrl/ti/pinctrl-ti-iodelay.c | 58 ++++++++++---------------
1 file changed, 24 insertions(+), 34 deletions(-)
--
2.45.2
next reply other threads:[~2024-07-09 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 20:37 Christophe JAILLET [this message]
2024-07-09 20:37 ` [PATCH 1/3] pinctrl: ti: ti-iodelay: Fix some error handling paths Christophe JAILLET
2024-07-09 20:37 ` [PATCH 2/3] pinctrl: ti: ti-iodelay: Constify struct ti_iodelay_reg_data Christophe JAILLET
2024-07-09 20:37 ` [PATCH 3/3] pinctrl: ti: ti-iodelay: Constify struct regmap_config Christophe JAILLET
2024-08-05 7:23 ` [PATCH 0/3] pinctrl: ti: ti-iodelay: Fix some error handling paths + 2 unrelated clean-ups Linus Walleij
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=cover.1720556038.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).