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.14-rc3 - take 2
Date: Sat, 15 Feb 2025 10:25:08 +0100 [thread overview]
Message-ID: <20250215092508.5849-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Here's a second attempt at the PR with fixes for the upcoming RC. The
sparse warning I mentioned in my previous email turned out to be a false
positive - the "offending" commit wasn't the culprit - but I removed it
anyway and will send it again next week with the sparse issue fixed
separately.
Details for this one are in the signed tag.
Please pull,
Bartosz
The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:
Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.14-rc3-take2
for you to fetch changes up to 7b4aebeecbbd5b5fe73e35fad3f62ed21aa7ef44:
gpiolib: Fix crash on error in gpiochip_get_ngpios() (2025-02-13 18:51:39 +0100)
----------------------------------------------------------------
gpio fixes for v6.14-rc3 - take 2
- fix interrupt handling issues in gpio-bcm-kona
- add an ACPI quirk for Acer Nitro ANV14 fixing an issue with spurious
wake up events
- add missing return value checks to gpio-stmpe
- fix a crash in error path in gpiochip_get_ngpios()
----------------------------------------------------------------
Andy Shevchenko (1):
gpiolib: Fix crash on error in gpiochip_get_ngpios()
Artur Weber (3):
gpio: bcm-kona: Fix GPIO lock/unlock for banks above bank 0
gpio: bcm-kona: Make sure GPIO bits are unlocked when requesting IRQ
gpio: bcm-kona: Add missing newline to dev_err format string
Mario Limonciello (1):
gpiolib: acpi: Add a quirk for Acer Nitro ANV14
Wentao Liang (1):
gpio: stmpe: Check return value of stmpe_reg_read in stmpe_gpio_irq_sync_unlock
drivers/gpio/gpio-bcm-kona.c | 71 ++++++++++++++++++++++++++++++++++++--------
drivers/gpio/gpio-stmpe.c | 15 ++++++++--
drivers/gpio/gpiolib-acpi.c | 14 +++++++++
drivers/gpio/gpiolib.c | 6 ++--
4 files changed, 87 insertions(+), 19 deletions(-)
next reply other threads:[~2025-02-15 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 9:25 Bartosz Golaszewski [this message]
2025-02-15 16:18 ` [GIT PULL] gpio fixes for v6.14-rc3 - take 2 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=20250215092508.5849-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