From: Sudeep Holla <sudeep.holla@arm.com>
To: gregkh@linuxfoundation.org
Cc: Vincenzo Mezzela <vincenzo.mezzela@gmail.com>,
rafael@kernel.org, javier.carrasco.cruz@gmail.com,
julia.lawall@inria.fr, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH 0/2 v4 RESEND] drivers: arch_topology: introduce automatic cleanup feature
Date: Mon, 10 Jun 2024 12:20:45 +0100 [thread overview]
Message-ID: <ZmbhjYdRC4ucv7Mh@bogus> (raw)
In-Reply-To: <20240607163350.392971-1-vincenzo.mezzela@gmail.com>
On Fri, Jun 07, 2024 at 06:33:48PM +0200, Vincenzo Mezzela wrote:
> Hi,
> I am resending this patch series rebased on top of -rc2 as the old one [1] might
> have got lost deep in the mailbox.
>
> This patch series introduces the automatic cleanup feature using the __free
> attribute. With this modification, resources allocated with __free are
> automatically released at the end of the scope.
>
>
[...]
> changes in v2:
> - check loop exit condition within the loop
> - add cleanup.h header
>
> changes in v3:
> - split patch in two
> - fix misalignment
> - fix checkpatch warnings
> - replace break with return statement where possible
>
> changes in v4:
> - fix commit subject
> - fix coding style
Hi Greg,
Can you please pick these couple of patches up directly for v6.11 as I
don't have anything else ATM ?
--
Regards,
Sudeep
next prev parent reply other threads:[~2024-06-10 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 16:33 [PATCH 0/2 v4 RESEND] drivers: arch_topology: introduce automatic cleanup feature Vincenzo Mezzela
2024-06-07 16:33 ` [PATCH 1/2 v4 RESEND] drivers: arch_topology: Refactor do-while loops Vincenzo Mezzela
2024-06-07 16:33 ` [PATCH 2/2 v4 RESEND] drivers: arch_topology: use __free attribute instead of of_node_put() Vincenzo Mezzela
2024-06-10 11:20 ` Sudeep Holla [this message]
2024-06-11 7:30 ` [PATCH 0/2 v4 RESEND] drivers: arch_topology: introduce automatic cleanup feature Greg KH
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=ZmbhjYdRC4ucv7Mh@bogus \
--to=sudeep.holla@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vincenzo.mezzela@gmail.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