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 <brgl@bgdev.pl>
Subject: [GIT PULL] gpio: fixes for v5.13
Date: Fri, 25 Jun 2021 14:33:20 +0200 [thread overview]
Message-ID: <20210625123320.26510-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following late fixes for the GPIO subsystem.
Best regards,
Bartosz Golaszewski
The following changes since commit dbec64b11c65d74f31427e2b9d5746fbf17bf840:
gpio: wcd934x: Fix shift-out-of-bounds error (2021-05-27 09:51:35 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.13
for you to fetch changes up to c6414e1a2bd26b0071e2b9d6034621f705dfd4c0:
gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP (2021-06-25 12:13:53 +0200)
----------------------------------------------------------------
gpio fixes for v5.13
- fix wake-up interrupt support on gpio-mxc
- zero the padding bytes in a structure passed to user-space in the GPIO
character device
- select HAS_IOPORT_MAP in two drivers that need it to fix a Kbuild issue
----------------------------------------------------------------
Gabriel Knezek (1):
gpiolib: cdev: zero padding during conversion to gpioline_info_changed
Johannes Berg (1):
gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP
Loic Poulain (1):
gpio: mxc: Fix disabled interrupt wake-up support
drivers/gpio/Kconfig | 2 ++
drivers/gpio/gpio-mxc.c | 2 +-
drivers/gpio/gpiolib-cdev.c | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
next reply other threads:[~2021-06-25 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 12:33 Bartosz Golaszewski [this message]
2021-06-25 17:48 ` [GIT PULL] gpio: fixes for v5.13 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=20210625123320.26510-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--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