From: Markus Elfring <Markus.Elfring@web.de>
To: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Christophe Leroy <chleroy@kernel.org>,
Dan Carpenter <error27@gmail.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Roy Pledge <Roy.Pledge@nxp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v3 0/2] soc: fsl: dpio: Use scope-based resource management in two functions
Date: Wed, 29 Jul 2026 13:36:41 +0200 [thread overview]
Message-ID: <709fefd1-821a-4cd1-8598-b1179a95ce52@web.de> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 29 Jul 2026 13:28:09 +0200
Some adjustment opportunities were picked up.
Markus Elfring (2):
Use scope-based resource management in dpaa2_io_store_create()
Use scope-based resource management in dpaa2_io_create()
v3:
* Dan Carpenter requested to add an #include directive.
https://lore.kernel.org/kernel-janitors/amdBqQfIsAjxMsqX@stanley.mountain/
* Ioana Ciornei requested to keep variable declarations at the start of
function implementations.
https://lore.kernel.org/kernel-janitors/6woig227u5snmdsrjfuw7gfcf3vk5iwaap4yf7ow6b6s3pba7z@yg4vmdoaak3h/
v2:
Christophe Leroy requested to apply the attribute “__free(kfree)”.
https://lore.kernel.org/kernel-janitors/d95d2f4c-f3cf-44eb-b61b-79ba7891674d@kernel.org/
drivers/soc/fsl/dpio/dpio-service.c | 37 ++++++++++-------------------
1 file changed, 12 insertions(+), 25 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-29 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 11:36 Markus Elfring [this message]
2026-07-29 11:42 ` [PATCH v3 1/2] soc: fsl: dpio: Use scope-based resource management in dpaa2_io_store_create() Markus Elfring
2026-07-29 11:44 ` [PATCH v3 2/2] soc: fsl: dpio: Use scope-based resource management in dpaa2_io_create() 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=709fefd1-821a-4cd1-8598-b1179a95ce52@web.de \
--to=markus.elfring@web.de \
--cc=Roy.Pledge@nxp.com \
--cc=chleroy@kernel.org \
--cc=error27@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=peterz@infradead.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 NNTP newsgroup(s).