From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.4
Date: Fri, 23 Jun 2023 12:10:12 +0200 [thread overview]
Message-ID: <20230623101012.114200-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the final round of fixes for this release from the GPIO subsystem.
Thanks
Bartosz
The following changes since commit 858fd168a95c5b9669aac8db6c14a9aeab446375:
Linux 6.4-rc6 (2023-06-11 14:35:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.4
for you to fetch changes up to ff7a1790fbf92f1bdd0966d3f0da3ea808ede876:
gpiolib: Fix irq_domain resource tracking for gpiochip_irqchip_add_domain() (2023-06-19 14:57:38 +0200)
----------------------------------------------------------------
gpio fixes for v6.4
- fix IRQ initialization in gpiochip_irqchip_add_domain()
- add a missing return value check for platform_get_irq() in gpio-sifive
- don't free irq_domains which GPIOLIB does not manage
----------------------------------------------------------------
Jiasheng Jiang (1):
gpio: sifive: add missing check for platform_get_irq
Jiawen Wu (1):
gpiolib: Fix GPIO chip IRQ initialization restriction
Michael Walle (1):
gpiolib: Fix irq_domain resource tracking for gpiochip_irqchip_add_domain()
drivers/gpio/gpio-sifive.c | 8 ++++++--
drivers/gpio/gpiolib.c | 11 ++++++++++-
include/linux/gpio/driver.h | 8 ++++++++
3 files changed, 24 insertions(+), 3 deletions(-)
next reply other threads:[~2023-06-23 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 10:10 Bartosz Golaszewski [this message]
2023-06-23 22:44 ` [GIT PULL] gpio: fixes for v6.4 pr-tracker-bot
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=20230623101012.114200-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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