From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Samuel Moelius <sam.moelius@trailofbits.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bamvor Jian Zhang <bamv2005@gmail.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Subject: [PATCH v1 0/3] gpio: Introduce helper to dispose IRQ mappings
Date: Wed, 21 Oct 2026 22:44:42 +0200 [thread overview]
Message-ID: <20261021204654.1001101-1-andriy.shevchenko@linux.intel.com> (raw)
I have noticed that a few drivers use almost the same code to dispose IRQ
mappings. This series to deduplicate the efforts. I only converted a couple
of the users (there are potentially more) in order to stay in the same
subsystem.
Andy Shevchenko (3):
gpiolib: Introduce devm_gpiochip_dispose_irq_mappings()
gpio: mockup: Replace custom devm_gpiochip_dispose_irq_mappings()
gpio: sim: Replace custom devm_gpiochip_dispose_irq_mappings()
drivers/gpio/gpio-mockup.c | 15 +--------------
drivers/gpio/gpio-sim.c | 17 ++++-------------
drivers/gpio/gpiolib-devres.c | 33 +++++++++++++++++++++++++++++++++
include/linux/gpio/driver.h | 4 ++++
4 files changed, 42 insertions(+), 27 deletions(-)
--
2.50.1
next reply other threads:[~2026-10-21 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 20:44 Andy Shevchenko [this message]
2026-10-21 20:44 ` [PATCH v1 1/3] gpiolib: Introduce devm_gpiochip_dispose_irq_mappings() Andy Shevchenko
2026-10-21 20:56 ` sashiko-bot
2026-10-23 7:38 ` kernel test robot
2026-10-21 20:44 ` [PATCH v1 2/3] gpio: mockup: Replace custom devm_gpiochip_dispose_irq_mappings() Andy Shevchenko
2026-10-21 20:44 ` [PATCH v1 3/3] gpio: sim: " Andy Shevchenko
2026-10-22 9:11 ` [PATCH v1 0/3] gpio: Introduce helper to dispose IRQ mappings Bartosz Golaszewski
2026-10-22 13:32 ` Andy Shevchenko
2026-10-22 14:05 ` Bartosz Golaszewski
2026-10-22 14:39 ` Andy Shevchenko
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=20261021204654.1001101-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bamv2005@gmail.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam.moelius@trailofbits.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.