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.1
Date: Thu, 8 Dec 2022 19:41:10 +0100 [thread overview]
Message-ID: <20221208184110.252270-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Here's the last PR with fixes for this release from the GPIO subsystem.
This is the same PR as last week sans the character device changes and with
one more tiny resource leak fix.
Please pull,
Bartosz Golaszewski
The following changes since commit b7b275e60bcd5f89771e865a8239325f86d9927d:
Linux 6.1-rc7 (2022-11-27 13:31:48 -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.1
for you to fetch changes up to 63ff545af73f759d1bd04198af8ed8577fb739fc:
gpio/rockchip: fix refcount leak in rockchip_gpiolib_register() (2022-12-06 10:10:46 +0100)
----------------------------------------------------------------
gpio fixes for v6.1
- fix a memory leak in gpiolib core
- fix reference leaks in gpio-amd8111 and gpio-rockchip
----------------------------------------------------------------
Wang Yufen (1):
gpio/rockchip: fix refcount leak in rockchip_gpiolib_register()
Xiongfeng Wang (1):
gpio: amd8111: Fix PCI device reference count leak
Zeng Heng (1):
gpiolib: fix memory leak in gpiochip_setup_dev()
drivers/gpio/gpio-amd8111.c | 4 ++++
drivers/gpio/gpio-rockchip.c | 1 +
drivers/gpio/gpiolib.c | 42 ++++++++++++++++++++++++++----------------
3 files changed, 31 insertions(+), 16 deletions(-)
next reply other threads:[~2022-12-08 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 18:41 Bartosz Golaszewski [this message]
2022-12-08 19:26 ` 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=20221208184110.252270-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
all inboxes | Powered by JetHome®