mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linusw@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [PATCH 0/3] gpio: lock device when calling device_is_bound()
Date: Mon, 18 May 2026 11:53:16 +0200	[thread overview]
Message-ID: <20260518-gpio-dev-lock-v1-0-cc4736f3ff0b@oss.qualcomm.com> (raw)

The kerneldoc for device_is_bound() says it must be called with the
device lock taken. Add missing synchronization to GPIO modules using it.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
---
Bartosz Golaszewski (3):
      gpio: sim: lock device when calling device_is_bound()
      gpio: aggregator: lock device when calling device_is_bound()
      gpio: virtuser: lock device when calling device_is_bound()

 drivers/gpio/gpio-aggregator.c |  9 ++++++---
 drivers/gpio/gpio-sim.c        | 11 +++++++----
 drivers/gpio/gpio-virtuser.c   |  9 ++++++---
 3 files changed, 19 insertions(+), 10 deletions(-)
---
base-commit: 5200f5f493f79f14bbdc349e402a40dfb32f23c8
change-id: 20260518-gpio-dev-lock-827253e58535

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>


             reply	other threads:[~2026-05-18  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  9:53 Bartosz Golaszewski [this message]
2026-05-18  9:53 ` [PATCH 1/3] gpio: sim: " Bartosz Golaszewski
2026-05-18  9:53 ` [PATCH 2/3] gpio: aggregator: " Bartosz Golaszewski
2026-05-18  9:53 ` [PATCH 3/3] gpio: virtuser: " Bartosz Golaszewski
2026-05-21 12:38 ` [PATCH 0/3] gpio: " 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=20260518-gpio-dev-lock-v1-0-cc4736f3ff0b@oss.qualcomm.com \
    --to=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=geert+renesas@glider.be \
    --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

all inboxes | Powered by JetHome®