From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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.4-rc4
Date: Fri, 26 May 2023 16:24:07 +0200 [thread overview]
Message-ID: <20230526142407.67019-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 Golaszewski
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.4-rc4
for you to fetch changes up to 3002b8642f016d7fe3ff56240dacea1075f6b877:
gpio-f7188x: fix chip name and pin count on Nuvoton chip (2023-05-23 10:47:41 +0200)
----------------------------------------------------------------
gpio fixes for v6.4-rc4
- fix incorrect output in in-tree gpio tools
- fix a shell coding issue in gpio-sim selftests
- correctly set the permissions for debugfs attributes exposed by gpio-mockup
- fix chip name and pin count in gpio-f7188x for one of the supported models
- fix numberspace pollution when using dynamically and statically allocated
GPIOs together
----------------------------------------------------------------
Andreas Kemnade (1):
gpiolib: fix allocation of mixed dynamic/static GPIOs
Henning Schild (1):
gpio-f7188x: fix chip name and pin count on Nuvoton chip
Milo Spadacini (1):
tools: gpio: fix debounce_period_us output of lsgpio
Mirsad Todorovac (1):
selftests: gpio: gpio-sim: Fix BUG: test FAILED due to recent change
Zev Weiss (1):
gpio: mockup: Fix mode of debugfs files
drivers/gpio/Kconfig | 2 +-
drivers/gpio/gpio-f7188x.c | 28 ++++++++++++++--------------
drivers/gpio/gpio-mockup.c | 2 +-
drivers/gpio/gpiolib.c | 2 ++
tools/gpio/lsgpio.c | 2 +-
tools/testing/selftests/gpio/gpio-sim.sh | 3 +++
6 files changed, 22 insertions(+), 17 deletions(-)
next reply other threads:[~2023-05-26 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 14:24 Bartosz Golaszewski [this message]
2023-05-26 20:38 ` [GIT PULL] gpio: fixes for v6.4-rc4 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=20230526142407.67019-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--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