mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linusw@kernel.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	brgl@kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [GIT PULL] gpio fixes for v7.3-rc7
Date: Thu,  8 Oct 2026 10:55:08 +0200	[thread overview]
Message-ID: <20261008085508.4815-1-bartosz.golaszewski@oss.qualcomm.com> (raw)

Linus,

Please pull the following set of GPIO driver fixes for the upcoming RC.

Thanks,
Bartosz

The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:

  Linux 7.3-rc5 (2026-09-27 13:55:01 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v7.3-rc7

for you to fetch changes up to 7efa1a1953cd6b20b23a3524d5b4b81789c6ef25:

  gpio: mpsse: fix race when arming the IRQ poll worker (2026-10-01 14:28:45 +0200)

----------------------------------------------------------------
gpio fixes for v7.3-rc7

- fix runtime PM leak in error path in gpio-xilinx
- fix race when arming the IRQ poll worker in gpio-mpsse
- fix devres cleanup path on probe error in gpio-exar

----------------------------------------------------------------
Fan Wu (1):
      gpio: mpsse: fix race when arming the IRQ poll worker

Ridham Khurana (1):
      gpio: xilinx: fix runtime PM leak on request error path

Sang-Hoon Choi (1):
      gpio: exar: initialize the ID before registering its cleanup

 drivers/gpio/gpio-exar.c   |  2 +-
 drivers/gpio/gpio-mpsse.c  | 24 ++++++++++++++++++++++--
 drivers/gpio/gpio-xilinx.c |  9 +--------
 3 files changed, 24 insertions(+), 11 deletions(-)

             reply	other threads:[~2026-10-08  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  8:55 Bartosz Golaszewski [this message]
2026-10-08 11:37 ` 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=20261008085508.4815-1-bartosz.golaszewski@oss.qualcomm.com \
    --to=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=linusw@kernel.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®