From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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.9-rc3
Date: Fri, 5 Apr 2024 19:58:03 +0200 [thread overview]
Message-ID: <20240405175803.299328-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following set of fixes for the next RC. Details are in
the signed tag as usual.
Thanks,
Bartosz
The following changes since commit 39cd87c4eb2b893354f3b850f916353f2658ae6f:
Linux 6.9-rc2 (2024-03-31 14:32:39 -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.9-rc3
for you to fetch changes up to 83092341e15d0dfee1caa8dc502f66c815ccd78a:
gpio: cdev: fix missed label sanitizing in debounce_setup() (2024-04-04 18:57:08 +0200)
----------------------------------------------------------------
gpio fixes for v6.9-rc3
- make sure GPIO devices are registered with the subsystem before trying
to return them to a caller of gpio_device_find()
- fix two issues with incorrect sanitization of the interrupt labels
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpio: cdev: check for NULL labels when sanitizing them for irqs
Hans de Goede (1):
gpiolib: Fix triggering "kobject: 'gpiochipX' is not initialized, yet" kobject_get() errors
Kent Gibson (1):
gpio: cdev: fix missed label sanitizing in debounce_setup()
drivers/gpio/gpiolib-cdev.c | 48 ++++++++++++++++++++++++++++++---------------
drivers/gpio/gpiolib.c | 3 +++
2 files changed, 35 insertions(+), 16 deletions(-)
next reply other threads:[~2024-04-05 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 17:58 Bartosz Golaszewski [this message]
2024-04-05 20:10 ` [GIT PULL] gpio: fixes for v6.9-rc3 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=20240405175803.299328-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--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