From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Helmut Grohne <h.grohne@intenta.de>
Subject: [GIT PULL] GPIO fixes for v4.7 take two
Date: Sun, 12 Jun 2016 01:48:41 +0200 [thread overview]
Message-ID: <CACRpkdYVVc0gRATS5nnavAyFjbTfKXSwe42CSCYvRVmHi9uGXg@mail.gmail.com> (raw)
Hi Linus,
a new bunch of GPIO fixes for v4.7. This time I am very grateful that
Ricardo Ribalda Delgado went in and fixed my stupid refcounting mistakes
in the removal path for GPIO chips. I had a feeling something was wrong
here and so it was. It exploded on OMAP and it fixes their
problem. Now it should be (more) solid.
The rest i compilation, Kconfig and driver fixes. Some tagged for stable.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit af8c34ce6ae32addda3788d54a7e340cad22516b:
Linux 4.7-rc2 (2016-06-05 14:31:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v4.7-3
for you to fetch changes up to b66b2a0adf0e48973b582e055758b9907a7eee7c:
gpio: bcm-kona: fix bcm_kona_gpio_reset() warnings (2016-06-08 14:04:35 +0200)
----------------------------------------------------------------
GPIO fixes for the v4.7 series:
- Fix a NULL pointer dereference when we are searching the
GPIO device list but one of the devices have been removed
(struct gpio_chip pointer is NULL).
- Fix unaligned reference counters: we were ending on +3 after
all said and done. It should be 0. Remove an extraneous
get_device(), and call cdev_del() followed by device_del()
in gpiochip_remove() instead and the count goes to zero and
calls the release() function properly.
- Fix a compile warning due to a missing #include in the
OF/device tree portions.
- Select ANON_INODES for GPIOLIB, we're using that for our
character device. Some randconfig tests disclosed the
problem.
- Make sure the Zynq driver clock runs also without CONFIG_PM
enabled
- Fix an off-by-one error in the 104-DIO-48E driver
- Fix warnings in bcm_kona_gpio_reset()
----------------------------------------------------------------
Ben Dooks (1):
gpio: bcm-kona: fix bcm_kona_gpio_reset() warnings
Helmut Grohne (1):
gpio: zynq: initialize clock even without CONFIG_PM
Linus Walleij (2):
gpio: include <linux/io-mapping.h> in gpiolib-of
gpio: select ANON_INODES
Ricardo Ribalda Delgado (2):
gpiolib: Fix NULL pointer deference
gpiolib: Fix unaligned used of reference counters
William Breathitt Gray (1):
gpio: 104-dio-48e: Fix control port offset computation off-by-one error
drivers/gpio/Kconfig | 1 +
drivers/gpio/gpio-104-dio-48e.c | 4 ++--
drivers/gpio/gpio-bcm-kona.c | 4 ++--
drivers/gpio/gpio-zynq.c | 7 +++++++
drivers/gpio/gpiolib-of.c | 1 +
drivers/gpio/gpiolib.c | 6 +++---
6 files changed, 16 insertions(+), 7 deletions(-)
reply other threads:[~2016-06-11 23:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACRpkdYVVc0gRATS5nnavAyFjbTfKXSwe42CSCYvRVmHi9uGXg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ben.dooks@codethink.co.uk \
--cc=h.grohne@intenta.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo.ribalda@gmail.com \
--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).