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.7-rc7
Date: Fri, 22 Dec 2023 11:07:31 +0100 [thread overview]
Message-ID: <20231222100731.10294-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Here's another round of fixes from the GPIO subsystem for this release cycle.
There's one commit adding synchronization to an ioctl() we overlooked
previously and another synchronization changeset for one of the drivers.
Details are in the signed tag.
Please pull,
Bartosz Golaszewski
The following changes since commit ceb6a6f023fd3e8b07761ed900352ef574010bcb:
Linux 6.7-rc6 (2023-12-17 15:19:28 -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.7-rc7
for you to fetch changes up to 1cc3542c76acb5f59001e3e562eba672f1983355:
gpio: dwapb: mask/unmask IRQ when disable/enale it (2023-12-21 11:19:01 +0100)
----------------------------------------------------------------
gpio fixes for v6.7-rc7
- add protection against GPIO device removal to an overlooked ioctl()
- synchronize the interrupt mask register manually in gpio-dwapb
----------------------------------------------------------------
Kent Gibson (1):
gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl()
xiongxin (1):
gpio: dwapb: mask/unmask IRQ when disable/enale it
drivers/gpio/gpio-dwapb.c | 12 ++++++++----
drivers/gpio/gpiolib-cdev.c | 16 ++++++++++++----
2 files changed, 20 insertions(+), 8 deletions(-)
next reply other threads:[~2023-12-22 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 10:07 Bartosz Golaszewski [this message]
2023-12-22 16:51 ` [GIT PULL] gpio: fixes for v6.7-rc7 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=20231222100731.10294-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