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.3
Date: Fri, 21 Apr 2023 12:07:13 +0200 [thread overview]
Message-ID: <20230421100713.39702-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull last two minor fixes from the GPIO subsystem for the upcoming
release. These are two fixes for potential deadlocks in GPIO drivers.
Bart
The following changes since commit 09a9639e56c01c7a00d6c0ca63f4c7c41abe075d:
Linux 6.3-rc6 (2023-04-09 11:15:57 -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.3
for you to fetch changes up to 2ce987d7eeb168b749494694ae3666de87fc356e:
gpio: 104-idi-48: Enable use_raw_spinlock for idi48_regmap_config (2023-04-11 21:08:31 +0200)
----------------------------------------------------------------
gpio fixes for v6.3
- use raw_spinlocks in regmaps that are used in interrupt context in
gpio-104-idi-48 and gpio-104-dio-48e
----------------------------------------------------------------
William Breathitt Gray (2):
gpio: 104-dio-48e: Enable use_raw_spinlock for dio48e_regmap_config
gpio: 104-idi-48: Enable use_raw_spinlock for idi48_regmap_config
drivers/gpio/gpio-104-dio-48e.c | 1 +
drivers/gpio/gpio-104-idi-48.c | 1 +
2 files changed, 2 insertions(+)
next reply other threads:[~2023-04-21 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:07 Bartosz Golaszewski [this message]
2023-04-21 17:08 ` [GIT PULL] gpio: fixes for v6.3 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=20230421100713.39702-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