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.4-rc1
Date: Thu, 19 Sep 2019 15:24:03 +0200 [thread overview]
Message-ID: <20190919132403.1835-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Hi Linus,
please pull the following set of fixes. Two are core code, one is a fix for
a driver. All are stable material.
The following changes since commit 4d856f72c10ecb060868ed10ff1b1453943fc6c8:
Linux 5.3 (2019-09-15 14:19:32 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-v5.4-rc1-fixes-for-linus
for you to fetch changes up to a94b734a563498ac4b8fff61179a3c2bba781a4e:
gpio: eic: sprd: Fix the incorrect EIC offset when toggling (2019-09-17 10:08:35 +0200)
----------------------------------------------------------------
gpio: fixes for v5.4-rc1
- fix a bug with emulated open-drain/source where lines' values can no longer
be changed
- fix getting nonexclusive gpiods from DT
- fix an incorrect offset for the level trigger in gpio-eic-sprd
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpiolib: don't clear FLAG_IS_OUT when emulating open-drain/open-source
Bruce Chen (1):
gpio: eic: sprd: Fix the incorrect EIC offset when toggling
Marco Felsch (1):
gpio: fix getting nonexclusive gpiods from DT
drivers/gpio/gpio-eic-sprd.c | 7 ++++---
drivers/gpio/gpiolib.c | 29 ++++++++++++++++++++---------
2 files changed, 24 insertions(+), 12 deletions(-)
next reply other threads:[~2019-09-19 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 13:24 Bartosz Golaszewski [this message]
2019-09-30 22:11 ` [GIT PULL] gpio: fixes for v5.4-rc1 Linus Walleij
2019-10-01 9:58 ` Bartosz Golaszewski
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=20190919132403.1835-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).