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.6-rc4
Date: Fri, 29 Sep 2023 14:31:24 +0200 [thread overview]
Message-ID: <20230929123124.19060-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following set of driver fixes for the next RC.
Thanks,
Bartosz
The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:
Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v6.6-rc4
for you to fetch changes up to 26d9e5640d2130ee16df7b1fb6a908f460ab004c:
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip (2023-09-27 09:12:09 +0200)
----------------------------------------------------------------
gpio fixes for v6.6-rc4
- fix a potential spinlock deadlock in gpio-timberdale
- mark the gpio-pmic-eic-sprd driver as one that can sleep
----------------------------------------------------------------
Chengfeng Ye (1):
gpio: timberdale: Fix potential deadlock on &tgpio->lock
Wenhua Lin (1):
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
drivers/gpio/gpio-pmic-eic-sprd.c | 1 +
drivers/gpio/gpio-timberdale.c | 5 +++--
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2023-09-29 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 12:31 Bartosz Golaszewski [this message]
2023-09-29 16:29 ` [GIT PULL] gpio: fixes for v6.6-rc4 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=20230929123124.19060-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;
as well as URLs for NNTP newsgroup(s).