Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>,
	Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org, Roy Pledge <Roy.Pledge@nxp.com>,
	kernel-janitors@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] soc: fsl: dpio: Use scope-based resource management in two functions
Date: Mon, 27 Jul 2026 11:57:50 +0200	[thread overview]
Message-ID: <0e740755-9eab-424e-803e-a956740994fb@kernel.org> (raw)
In-Reply-To: <d2e5df25-c8b7-4ee6-8ebf-1725542baabd@web.de>

Hi Ioana,

Le 06/07/2026 à 12:36, Markus Elfring a écrit :
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 6 Jul 2026 11:42:10 +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()
> 

As the (new) maintainer of drivers/soc/fsl/dpio, could you have a look 
at this series ?

Thanks
Christophe

> 
> v2:
> Christophe Leroy requested to apply the attribute “__free(kfree)”.
> 
> 
>   drivers/soc/fsl/dpio/dpio-service.c | 37 ++++++++++-------------------
>   1 file changed, 12 insertions(+), 25 deletions(-)
> 



      parent reply	other threads:[~2026-07-27  9:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 10:02 [PATCH] soc: fsl: dpio: Use common error handling code in two functions Markus Elfring
2026-07-04  9:19 ` Christophe Leroy (CS GROUP)
2026-07-04 10:11   ` Markus Elfring
2026-07-06 10:36   ` [PATCH v2 0/2] soc: fsl: dpio: Use scope-based resource management " Markus Elfring
2026-07-06 10:38     ` [PATCH v2 1/2] soc: fsl: dpio: Use scope-based resource management in dpaa2_io_store_create() Markus Elfring
2026-07-27 11:31       ` Dan Carpenter
2026-07-27 12:08       ` Ioana Ciornei
2026-07-27 12:24         ` [v2 " Markus Elfring
2026-07-27 12:46           ` Ioana Ciornei
2026-07-27 12:52             ` Markus Elfring
2026-07-06 10:40     ` [PATCH v2 2/2] soc: fsl: dpio: Use scope-based resource management in dpaa2_io_create() Markus Elfring
2026-07-27 11:32       ` Dan Carpenter
2026-07-27 12:14         ` [v2 " Markus Elfring
2026-07-27 12:09       ` [PATCH v2 " Ioana Ciornei
2026-07-27 13:14         ` [v2 " Markus Elfring
2026-07-27  9:57     ` Christophe Leroy (CS GROUP) [this message]

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=0e740755-9eab-424e-803e-a956740994fb@kernel.org \
    --to=chleroy@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=Roy.Pledge@nxp.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 \
    /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