From: Marco Scardovi <mscardovi95@gmail.com>
To: mika.westerberg@intel.com
Cc: mathias.nyman@intel.com, andriy.shevchenko@intel.com,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marco Scardovi <mscardovi95@gmail.com>
Subject: [PATCH v2 0/3] gpio: acpi: modernize resource management using cleanup.h
Date: Wed, 6 May 2026 14:35:33 +0200 [thread overview]
Message-ID: <20260506123637.1077421-2-mscardovi95@gmail.com> (raw)
In-Reply-To: <20260506123637.1077421-1-mscardovi95@gmail.com>
*** BLURB HERE ***
Hi Mika,
thanks for the quick reply. Unfortunately I noticed too late that thunderbird had
broken my patch during copy/paste. I'm pushing it again using git send-mail.
I've divided tha patch in 3 smaller pieces: let me know if it is ok for you and
Andy. In the meantime I'm testing it against KASAN and kmemleak as You suggested.
Let me know if there's anything else I need to improve.
Marco Scardovi (3):
gpio: acpi: modernize resource management using cleanup.h
gpio: acpi: modernize resource management using cleanup.h
gpio: acpi: modernize resource management using cleanup.h
drivers/gpio/gpiolib-acpi-core.c | 68 ++++++++++++++++----------------
1 file changed, 35 insertions(+), 33 deletions(-)
--
2.54.0
next prev parent reply other threads:[~2026-05-06 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260506113215.GK6785@://intel.com>
2026-05-06 12:34 ` [PATCH v2 0/3] gpio: acpi: modernize resource management using cleanup.h Marco Scardovi
2026-05-06 12:49 ` Andy Shevchenko
2026-05-06 12:35 ` Marco Scardovi
2026-05-06 12:35 ` Marco Scardovi [this message]
2026-05-06 12:35 ` [PATCH v2 1/3] [PATCH 1/3] " Marco Scardovi
2026-05-06 12:51 ` Andy Shevchenko
2026-05-06 12:35 ` [PATCH v2 2/3] [PATCH 2/3] " Marco Scardovi
2026-05-06 12:35 ` [PATCH v2 3/3] [PATCH 3/3] " Marco Scardovi
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=20260506123637.1077421-2-mscardovi95@gmail.com \
--to=mscardovi95@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mika.westerberg@intel.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