Linux GPIO subsystem development
 help / color / mirror / Atom feed
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.3-rc1
Date: Mon, 15 Jul 2019 11:59:03 +0200	[thread overview]
Message-ID: <20190715095903.18307-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

Linus,

please pull the following fixes applied to my tree during this merge window.

The following changes since commit fec88ab0af9706b2201e5daf377c5031c62d11f7:

  Merge tag 'for-linus-hmm' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2019-07-14 19:42:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-v5.3-rc1-fixes-for-linus

for you to fetch changes up to 19ec11a2233d24a7811836fa735203aaccf95a23:

  gpio: em: remove the gpiochip before removing the irq domain (2019-07-15 11:52:42 +0200)

----------------------------------------------------------------
GPIO fixes for v5.3-rc1

- silence error messages on probe deferral in gpio-davinci
- fix a memory leak in gpiolib-of
- fix a potential use-after-free error in gpio-em

----------------------------------------------------------------
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

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   |  1 +
 3 files changed, 19 insertions(+), 20 deletions(-)

             reply	other threads:[~2019-07-15  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15  9:59 Bartosz Golaszewski [this message]
2019-07-16  9:13 ` [GIT PULL] gpio fixes for v5.3-rc1 Linus Walleij

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=20190715095903.18307-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