From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3 0/5] pinctrl: at91: Cleanups
Date: Wed, 15 Feb 2023 15:42:37 +0200 [thread overview]
Message-ID: <20230215134242.37618-1-andriy.shevchenko@linux.intel.com> (raw)
The kasprintf() patch makes me look into the driver code and besides
missed fix, there is a room to improve. Hence this series.
Compile tested only.
Changes in v3:
- added tags (Claudiu)
- dropped unrelated curly bracket change (Claudiu)
Changes in v2:
- fixed compilation errors (LKP)
Andy Shevchenko (5):
pinctrl: at91: use devm_kasprintf() to avoid potential leaks (part 2)
pinctrl: at91: Don't mix non-devm calls with devm ones
pinctrl: at91: Use of_device_get_match_data()
pinctrl: at91: Use dev_err_probe() instead of custom messaging
pinctrl: at91: Utilise temporary variable for struct device
drivers/pinctrl/pinctrl-at91.c | 161 ++++++++++++++-------------------
1 file changed, 66 insertions(+), 95 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-15 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 13:42 Andy Shevchenko [this message]
2023-02-15 13:42 ` [PATCH v3 1/5] pinctrl: at91: use devm_kasprintf() to avoid potential leaks (part 2) Andy Shevchenko
2023-02-15 13:42 ` [PATCH v3 2/5] pinctrl: at91: Don't mix non-devm calls with devm ones Andy Shevchenko
2023-02-15 13:42 ` [PATCH v3 3/5] pinctrl: at91: Use of_device_get_match_data() Andy Shevchenko
2023-02-15 13:42 ` [PATCH v3 4/5] pinctrl: at91: Use dev_err_probe() instead of custom messaging Andy Shevchenko
2023-02-15 13:42 ` [PATCH v3 5/5] pinctrl: at91: Utilise temporary variable for struct device Andy Shevchenko
2023-02-17 11:54 ` Claudiu.Beznea
2023-02-17 11:59 ` Andy Shevchenko
2023-02-27 21:44 ` Linus Walleij
2023-02-27 22:20 ` Andy Shevchenko
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=20230215134242.37618-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--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=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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).