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 take one
Date: Wed, 17 Jul 2019 17:24:38 +0200 [thread overview]
Message-ID: <CACRpkdYOahn84UxZ_-YAQsP+4W+HQCAL7xEJieEDd53xLgaWfw@mail.gmail.com> (raw)
Hi Linus,
some fixes arrived early so let's merge them early so we
have as little problems as possible in -rc1.
This is based on the most recent HEAD commit that day.
Please pull it in, details in the signed tag.
Yours,
Linus Walleij
The following changes since commit 9637d517347e80ee2fe1c5d8ce45ba1b88d8b5cd:
Merge tag 'for-linus-20190715' of git://git.kernel.dk/linux-block
(2019-07-15 21:20:52 -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-2
for you to fetch changes up to 88785b7fa74ae2dc52f879140b976984b5374c79:
Merge tag 'gpio-v5.3-rc1-fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux into fixes
(2019-07-16 11:12:14 +0200)
----------------------------------------------------------------
GPIO fixes for the v5.3 merge window:
- Revert a SPIO GPIO fix that didn't fix anything instead created new
problems.
- Remove the EM GPIO irqdomain in a safe manner.
- Fix a memory leak in the gpio quirks.
- Make the DaVinci error path silent on probe deferral.
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpio: em: remove the gpiochip before removing the irq domain
Keerthy (1):
gpio: davinci: silence error prints in case of EPROBE_DEFER
Linus Walleij (2):
Revert "gpio/spi: Fix spi-gpio regression on active high CS"
Merge tag 'gpio-v5.3-rc1-fixes-for-linus' of
git://git.kernel.org/.../brgl/linux into fixes
Nishka Dasgupta (1):
gpiolib: of: fix a memory leak in of_gpio_flags_quirks()
drivers/gpio/gpio-davinci.c | 5 +++--
drivers/gpio/gpio-em.c | 33 +++++++++++++++------------------
drivers/gpio/gpiolib-of.c | 10 ++--------
3 files changed, 20 insertions(+), 28 deletions(-)
next reply other threads:[~2019-07-17 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 15:24 Linus Walleij [this message]
2019-07-17 20:20 ` [GIT PULL] GPIO fixes for v5.3 take one 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=CACRpkdYOahn84UxZ_-YAQsP+4W+HQCAL7xEJieEDd53xLgaWfw@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).