From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linusw@kernel.org>, Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [PATCH 0/4] gpio: shared: fix some bugs in unregister and error paths
Date: Sat, 06 Dec 2025 12:53:52 +0100 [thread overview]
Message-ID: <20251206-gpio-shared-teardown-fixes-v1-0-35ac458cfce1@oss.qualcomm.com> (raw)
Here are a couple more fixes for shared GPIOs that I want to send before
the end of the merge window.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
---
Bartosz Golaszewski (4):
gpio: shared: fix NULL-pointer dereference in teardown path
gpio: shared: check if a reference is populated before cleaning its resources
gpio: shared: fix auxiliary device cleanup order
gpio: shared: make locking more fine-grained
drivers/gpio/gpiolib-shared.c | 50 ++++++++++++++++++++++++++-----------------
1 file changed, 30 insertions(+), 20 deletions(-)
---
base-commit: 057c46412cd90e432a73f650cdd75b56f755a082
change-id: 20251205-gpio-shared-teardown-fixes-d1e2429333c7
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
next reply other threads:[~2025-12-06 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 11:53 Bartosz Golaszewski [this message]
2025-12-06 11:53 ` [PATCH 1/4] gpio: shared: fix NULL-pointer dereference in teardown path Bartosz Golaszewski
2025-12-06 11:53 ` [PATCH 2/4] gpio: shared: check if a reference is populated before cleaning its resources Bartosz Golaszewski
2025-12-06 11:53 ` [PATCH 3/4] gpio: shared: fix auxiliary device cleanup order Bartosz Golaszewski
2025-12-06 11:53 ` [PATCH 4/4] gpio: shared: make locking more fine-grained Bartosz Golaszewski
2025-12-09 6:19 ` [PATCH 0/4] gpio: shared: fix some bugs in unregister and error paths Bartosz Golaszewski
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=20251206-gpio-shared-teardown-fixes-v1-0-35ac458cfce1@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).