Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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.15-rc7
Date: Fri, 16 May 2025 12:12:15 +0200	[thread overview]
Message-ID: <20250516101215.5822-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Linus,

Please pull the following set of GPIO fixes for the next RC.

Thanks,
Bartosz

The following changes since commit 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3:

  Linux 6.15-rc6 (2025-05-11 14:54:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v6.15-rc7

for you to fetch changes up to 7118be7c6072f40391923543fdd1563b8d56377c:

  gpio: virtuser: fix potential out-of-bound write (2025-05-13 12:59:30 +0200)

----------------------------------------------------------------
gpio fixes for v6.15-rc7

- fix an interrupt storm on system wake-up in gpio-pca953x
- fix an out-of-bounds write in gpio-virtuser
- update MAINTAINERS with an entry for the sloppy logic analyzer

----------------------------------------------------------------
Emanuele Ghidoli (1):
      gpio: pca953x: fix IRQ storm on system wake up

Markus Burri (1):
      gpio: virtuser: fix potential out-of-bound write

Wolfram Sang (1):
      MAINTAINERS: add me as maintainer for the gpio sloppy logic analyzer

 MAINTAINERS                  |  7 +++++++
 drivers/gpio/gpio-pca953x.c  |  6 ++++++
 drivers/gpio/gpio-virtuser.c | 12 ++++++++++--
 3 files changed, 23 insertions(+), 2 deletions(-)

             reply	other threads:[~2025-05-16 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 10:12 Bartosz Golaszewski [this message]
2025-05-16 16:44 ` [GIT PULL] gpio fixes for v6.15-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=20250516101215.5822-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --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