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.14-rc1
Date: Thu, 30 Jan 2025 10:34:54 +0100	[thread overview]
Message-ID: <20250130093454.17264-1-brgl@bgdev.pl> (raw)

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

Linus,

Please pull the following set of GPIO fixes for the upcoming rc1.

Thanks,
Bartosz

The following changes since commit 4abae5b6af811ab2b53aa761bf9ae2139757d594:

  Merge tag 'gpio-updates-for-v6.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux (2025-01-22 08:47:54 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v6.14-rc1

for you to fetch changes up to f8524ac33cd452aef5384504b3264db6039a455e:

  selftests: gpio: gpio-sim: Fix missing chip disablements (2025-01-23 15:44:48 +0100)

----------------------------------------------------------------
gpio fixes for v6.14-rc1

- update gpio-sim selftests to not fail now that we no longer allow
  rmdir() on configfs entries of active devices
- remove leftover code from gpio-mxc

----------------------------------------------------------------
Ahmad Fatoum (1):
      gpio: mxc: remove dead code after switch to DT-only

Koichiro Den (1):
      selftests: gpio: gpio-sim: Fix missing chip disablements

 drivers/gpio/gpio-mxc.c                  |  3 +--
 tools/testing/selftests/gpio/gpio-sim.sh | 31 +++++++++++++++++++++++++------
 2 files changed, 26 insertions(+), 8 deletions(-)

             reply	other threads:[~2025-01-30  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30  9:34 Bartosz Golaszewski [this message]
2025-01-30 18:56 ` [GIT PULL] gpio fixes for v6.14-rc1 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=20250130093454.17264-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