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-rc2
Date: Fri, 29 Mar 2024 11:54:52 +0100 [thread overview]
Message-ID: <20240329105452.17036-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following set of fixes for the next RC.
Thanks,
Bartosz
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -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-rc2
for you to fetch changes up to 5c887b65bbd1a3fc28e2e20399acede0baa83edb:
gpiolib: Fix debug messaging in gpiod_find_and_request() (2024-03-26 12:50:50 +0100)
----------------------------------------------------------------
gpio fixes for v6.9-rc2
- fix a procfs failure when requesting an interrupt with a label containing
the '/' character
- add missing stubs for GPIO lookup functions for !GPIOLIB
- fix debug messages that would print "(null)" for NULL strings
----------------------------------------------------------------
Andy Shevchenko (1):
gpiolib: Fix debug messaging in gpiod_find_and_request()
Bartosz Golaszewski (1):
gpio: cdev: sanitize the label before requesting the interrupt
Mark Brown (1):
gpiolib: Add stubs for GPIO lookup functions
drivers/gpio/gpiolib-cdev.c | 38 ++++++++++++++++++++++++++++++++------
drivers/gpio/gpiolib.c | 32 ++++++++++++++++++--------------
include/linux/gpio/driver.h | 17 +++++++++++++++--
3 files changed, 65 insertions(+), 22 deletions(-)
next reply other threads:[~2024-03-29 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 10:54 Bartosz Golaszewski [this message]
2024-03-29 19:27 ` 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=20240329105452.17036-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
all inboxes | Powered by JetHome®