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.12-rc2
Date: Fri, 4 Oct 2024 16:21:00 +0200 [thread overview]
Message-ID: <20241004142100.53097-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.
Bartosz
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -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.12-rc2
for you to fetch changes up to 7b99b5ab885993bff010ebcd93be5e511c56e28a:
gpiolib: Fix potential NULL pointer dereference in gpiod_get_label() (2024-10-03 20:51:47 +0200)
----------------------------------------------------------------
gpio fixes for v6.12-rc2
- fix a potential NULL-pointer dereference in gpiolib core
- fix a probe() regression from the v6.12 merge window and an older bug
leading to missed interrupts in gpio-davinci
----------------------------------------------------------------
Emanuele Ghidoli (1):
gpio: davinci: fix lazy disable
Lad Prabhakar (1):
gpiolib: Fix potential NULL pointer dereference in gpiod_get_label()
Vignesh Raghavendra (1):
gpio: davinci: Fix condition for irqchip registration
drivers/gpio/gpio-davinci.c | 10 +++++-----
drivers/gpio/gpiolib.c | 4 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2024-10-04 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 14:21 Bartosz Golaszewski [this message]
2024-10-04 19:04 ` 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=20241004142100.53097-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®