From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [GIT PULL] GPIO fixes for v5.3
Date: Sun, 8 Sep 2019 09:00:26 +0100 [thread overview]
Message-ID: <CACRpkdYEPBOFnKvNiH0kSOZWTujMaMNhQQgRTGSZUosbbqAdkQ@mail.gmail.com> (raw)
Hi Linus,
some (hopefully last) small GPIO fix for the v5.3 series.
Just affecting PCA953x expanders. Details in the tag.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit a55aa89aab90fae7c815b0551b07be37db359d76:
Linux 5.3-rc6 (2019-08-25 12:01:23 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v5.3-5
for you to fetch changes up to 89f2c0425cb51e38d6b39795c08d55421bec680c:
Merge tag 'gpio-v5.3-rc7-fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux into fixes
(2019-08-30 15:28:04 +0200)
----------------------------------------------------------------
GPIO fixes for the v5.3 series:
all related to the PCA953x driver when handling chips with
more than 8 ports, now that works again.
----------------------------------------------------------------
David Jander (2):
gpio: pca953x: correct type of reg_direction
gpio: pca953x: use pca953x_read_regs instead of regmap_bulk_read
Linus Walleij (1):
Merge tag 'gpio-v5.3-rc7-fixes-for-linus' of
git://git.kernel.org/.../brgl/linux into fixes
drivers/gpio/gpio-pca953x.c | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
next reply other threads:[~2019-09-08 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 8:00 Linus Walleij [this message]
2019-09-08 17:25 ` [GIT PULL] GPIO fixes for v5.3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-08-24 21:17 Linus Walleij
2019-08-24 21:50 ` 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=CACRpkdYEPBOFnKvNiH0kSOZWTujMaMNhQQgRTGSZUosbbqAdkQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bgolaszewski@baylibre.com \
--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;
as well as URLs for NNTP newsgroup(s).