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 <brgl@bgdev.pl>
Subject: [GIT PULL] gpio: fixes for v5.11
Date: Thu, 11 Feb 2021 15:18:43 +0100 [thread overview]
Message-ID: <20210211141843.32699-1-brgl@bgdev.pl> (raw)
Linus,
This is hopefully the last batch of fixes for this release cycle. We
have a minor fix for a Kconfig regression as well as fixes for older
bugs in gpio-ep93xx.
Please pull,
Bartosz
The following changes since commit 92bf22614b21a2706f4993b278017e437f7785b3:
Linux 5.11-rc7 (2021-02-07 13:57:38 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.11
for you to fetch changes up to 28dc10eb77a2db7681b08e3b109764bbe469e347:
gpio: ep93xx: Fix single irqchip with multi gpiochips (2021-02-10 14:47:27 +0100)
----------------------------------------------------------------
gpio fixes for v5.11
- don't build gpio-mxs unconditionally with COMPILE_TEST enabled
- fix two problems with interrupt handling in gpio-ep93xx
----------------------------------------------------------------
Geert Uytterhoeven (1):
gpio: mxs: GPIO_MXS should not default to y unconditionally
Nikita Shubin (2):
gpio: ep93xx: fix BUG_ON port F usage
gpio: ep93xx: Fix single irqchip with multi gpiochips
drivers/gpio/Kconfig | 3 +-
drivers/gpio/gpio-ep93xx.c | 216 +++++++++++++++++++++++++--------------------
2 files changed, 120 insertions(+), 99 deletions(-)
next reply other threads:[~2021-02-11 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 14:18 Bartosz Golaszewski [this message]
2021-02-11 20:22 ` [GIT PULL] gpio: fixes for v5.11 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=20210211141843.32699-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--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