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-rc7
Date: Fri, 18 Aug 2023 20:16:49 +0200 [thread overview]
Message-ID: <20230818181649.20814-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following fixes from the GPIO subsystem. Details are in the
signed tag.
Thanks,
Bartosz
The following changes since commit 2ccdd1b13c591d306f0401d98dedc4bdcd02b421:
Linux 6.5-rc6 (2023-08-13 11:29:55 -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-rc7
for you to fetch changes up to 3386fb86ecdef0d39ee3306aea8ec290e61b934f:
gpiolib: fix reference leaks when removing GPIO chips still in use (2023-08-16 13:35:50 +0200)
----------------------------------------------------------------
gpio fixes for v6.5-rc6
- fix a regression in the sysfs interface
- fix a reference counting bug that's been around for years
- MAINTAINERS update
----------------------------------------------------------------
Andy Shevchenko (1):
gpiolib: sysfs: Do unexport GPIO when user asks for it
Bartosz Golaszewski (1):
gpiolib: fix reference leaks when removing GPIO chips still in use
Michael Walle (1):
MAINTAINERS: add content regex for gpio-regmap
MAINTAINERS | 1 +
drivers/gpio/gpiolib-sysfs.c | 7 +++++--
drivers/gpio/gpiolib.c | 16 +++++++++++-----
3 files changed, 17 insertions(+), 7 deletions(-)
next reply other threads:[~2023-08-18 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 18:16 Bartosz Golaszewski [this message]
2023-08-18 18:55 ` [GIT PULL] gpio: fixes for v6.5-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=20230818181649.20814-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