linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-gpio@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Gary Bisson <gary.bisson@boundarydevices.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Peng Fan <van.freenix@gmail.com>, Shawn Guo <shawnguo@kernel.org>,
	Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: [PATCH 00/10] pinctrl: freescale: Fine-tuning for ten function implementations
Date: Fri, 14 Apr 2017 11:00:20 +0200	[thread overview]
Message-ID: <59fae4ac-9e07-232a-4843-92dd9e0cf2ef@users.sourceforge.net> (raw)

From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 14 Apr 2017 10:45:43 +0200

Some update suggestions were taken into account
from static source code analysis.

Markus Elfring (10):
  imx: Use kmalloc_array() in imx_dt_node_to_map()
  imx: Use devm_kcalloc() in two functions
  imx: Return directly after a failed devm_kcalloc() in imx_pinctrl_parse_functions()
  imx: Improve another size determination in imx_pinctrl_parse_functions()
  imx: Use devm_kmalloc_array() in imx_pinctrl_probe()
  imx: Use seq_putc() in imx_pinconf_group_dbg_show()
  imx: Use seq_puts() in imx_pinconf_dbg_show()
  imx1-core: Use kmalloc_array() in imx_dt_node_to_map()
  mxs: Use devm_kcalloc() in two functions
  mxs: Use kcalloc() in mxs_dt_node_to_map()

 drivers/pinctrl/freescale/pinctrl-imx.c       | 31 +++++++++++++++------------
 drivers/pinctrl/freescale/pinctrl-imx1-core.c |  2 +-
 drivers/pinctrl/freescale/pinctrl-mxs.c       | 13 +++++------
 3 files changed, 25 insertions(+), 21 deletions(-)

-- 
2.12.2


             reply	other threads:[~2017-04-14  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  9:00 SF Markus Elfring [this message]
2017-04-14  9:03 ` [PATCH 1/10] pinctrl: imx: Use kmalloc_array() in imx_dt_node_to_map() SF Markus Elfring
2017-04-14  9:07 ` [PATCH 02/10] pinctrl: imx: Use devm_kcalloc() in two functions SF Markus Elfring
2017-04-14  9:11 ` [PATCH 03/10] pinctrl: imx: Return directly after a failed devm_kcalloc() in imx_pinctrl_parse_functions() SF Markus Elfring
2017-04-14  9:14 ` [PATCH 04/10] pinctrl: imx: Improve another size determination " SF Markus Elfring
2017-04-14  9:15 ` [PATCH 05/10] pinctrl: imx: Use devm_kmalloc_array() in imx_pinctrl_probe() SF Markus Elfring
2017-04-14  9:17 ` [PATCH 06/10] pinctrl: imx: Use seq_putc() in imx_pinconf_group_dbg_show() SF Markus Elfring
2017-04-14  9:19 ` [PATCH 07/10] pinctrl: imx: Use seq_puts() in imx_pinconf_dbg_show() SF Markus Elfring
2017-04-14  9:20 ` [PATCH 08/10] pinctrl: imx1-core: Use kmalloc_array() in imx_dt_node_to_map() SF Markus Elfring
2017-04-14  9:22 ` [PATCH 09/10] pinctrl: mxs: Use devm_kcalloc() in two functions SF Markus Elfring
2017-04-14  9:23 ` [PATCH 10/10] pinctrl: mxs: Use kcalloc() in mxs_dt_node_to_map() SF Markus Elfring

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=59fae4ac-9e07-232a-4843-92dd9e0cf2ef@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=arnd@arndb.de \
    --cc=gary.bisson@boundarydevices.com \
    --cc=ldewangan@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=shawnguo@kernel.org \
    --cc=van.freenix@gmail.com \
    --cc=vladimir_zapolskiy@mentor.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).