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.5-rc6
Date: Sat, 12 Aug 2023 20:26:25 +0200 [thread overview]
Message-ID: <20230812182625.5059-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following two one-liners from the GPIO subsystem for the
next RC.
Bartosz
The following changes since commit 6eaae198076080886b9e7d57f4ae06fa782f90ef:
Linux 6.5-rc3 (2023-07-23 15:24:10 -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.5-rc6
for you to fetch changes up to 33f83d13ded164cd49ce2a3bd2770115abc64e6f:
gpio: ws16c48: Fix off-by-one error in WS16C48 resource region extent (2023-08-11 21:31:59 +0200)
----------------------------------------------------------------
gpio fixes for v6.5-rc6
- mark virtual chips exposed by gpio-sim as ones that can sleep (callbacks
must not be called from interrupt context)
- fix an off-by-one error in gpio-ws16c48
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpio: sim: mark the GPIO chip as a one that can sleep
William Breathitt Gray (1):
gpio: ws16c48: Fix off-by-one error in WS16C48 resource region extent
drivers/gpio/gpio-sim.c | 1 +
drivers/gpio/gpio-ws16c48.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2023-08-12 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 18:26 Bartosz Golaszewski [this message]
2023-08-12 18:37 ` [GIT PULL] gpio: fixes for v6.5-rc6 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=20230812182625.5059-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