From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [GIT PULL] gpio: fixes for v5.8-rc3
Date: Thu, 25 Jun 2020 18:08:46 +0200 [thread overview]
Message-ID: <20200625160846.5717-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Hi Linus,
please pull the following fixes for gpio-pca953x collected since the
merge window.
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v5.8-rc3
for you to fetch changes up to 5d8913504ccfeea6120df5ae1c6f4479ff09b931:
gpio: pca953x: Fix GPIO resource leak on Intel Galileo Gen 2 (2020-06-22 18:51:53 +0200)
----------------------------------------------------------------
gpio fixes for v5.8-rc3
- several fixes for gpio-pca953x
----------------------------------------------------------------
Andy Shevchenko (5):
gpio: pca953x: Synchronize interrupt handler properly
gpio: pca953x: Override IRQ for one of the expanders on Galileo Gen 2
gpio: pca953x: Fix direction setting when configure an IRQ
gpio: pca953x: disable regmap locking for automatic address incrementing
gpio: pca953x: Fix GPIO resource leak on Intel Galileo Gen 2
drivers/gpio/gpio-pca953x.c | 99 ++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 94 insertions(+), 5 deletions(-)
next reply other threads:[~2020-06-25 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 16:08 Bartosz Golaszewski [this message]
2020-06-26 21:53 ` [GIT PULL] gpio: fixes for v5.8-rc3 Linus Walleij
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=20200625160846.5717-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).