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>,
Johan Hovold <johan@kernel.org>,
Sonic Zhang <sonic.adi@gmail.com>,
Tony Lindgren <tony@atomide.com>
Subject: [GIT PULL] GPIO fixes for v3.19 last take
Date: Mon, 2 Feb 2015 14:53:38 +0100 [thread overview]
Message-ID: <CACRpkdZCkfNW1XO7BKhHZAERNZ8DjmECsiyAx+KE=1jgcr+MWA@mail.gmail.com> (raw)
Hi Linus,
there is a high bug-spot activity in GPIO this merge window, much
due to Johan Hovolds spearheading into actually exercising the
removal path for GPIO chips, something that was never really
exercised before.
The other two fixes are augmenting erroneous behaviours in two
specific drivers for minor systems.
I know it's late, but please pull this in for v3.19.
Yours,
Linus Walleij
The following changes since commit 26bc420b59a38e4e6685a73345a0def461136dce:
Linux 3.19-rc6 (2015-01-25 20:04:41 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v3.19-5
for you to fetch changes up to 49d2ca84e433dab854c7a866bc6add09cfab682d:
gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low
(2015-01-30 10:29:33 +0100)
----------------------------------------------------------------
Yet more GPIO fixes for the v3.19 series:
- Two fixes stabilizing that which was never stable before:
removal of GPIO chips, now let's stop leaking memory.
- Make sure OMAP IRQs are usable when the irqchip API
is used orthogonally to the gpiochip API.
- Provide a default GPIO base for the mcp23s08 driver.
----------------------------------------------------------------
Johan Hovold (2):
gpio: sysfs: fix memory leak in gpiod_export_link
gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low
Sonic Zhang (1):
gpio: mcp23s08: handle default gpio base
Tony Lindgren (1):
gpio: omap: Fix bad device access with setup_irq()
drivers/gpio/gpio-mcp23s08.c | 17 ++++++++++-------
drivers/gpio/gpio-omap.c | 39 +++++++++++++++++++++++++++++++++------
drivers/gpio/gpiolib-sysfs.c | 3 ++-
3 files changed, 45 insertions(+), 14 deletions(-)
reply other threads:[~2015-02-02 13:53 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='CACRpkdZCkfNW1XO7BKhHZAERNZ8DjmECsiyAx+KE=1jgcr+MWA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=johan@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.adi@gmail.com \
--cc=tony@atomide.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).