public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [GIT PULL] gpio: fixes for v5.11-rc7
Date: Wed,  3 Feb 2021 14:08:57 +0100	[thread overview]
Message-ID: <20210203130857.17648-1-brgl@bgdev.pl> (raw)

Linus,

here are some more fixes from the GPIO subsystem for this release. This
time it's only core fixes. Details are in the signed tag.

Please pull,
Bartosz

The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04:

  Linux 5.11-rc5 (2021-01-24 16:47:14 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.11-rc7

for you to fetch changes up to c07ea8d0b170c0cf6592a53981841c7973e142ea:

  gpio: gpiolib: remove shadowed variable (2021-02-01 13:24:28 +0100)

----------------------------------------------------------------
gpio fixes for v5.11-rc7

- fix a memory leak in error path in gpiolib
- clear debounce period in output mode in the character device code
- remove shadowed variable

----------------------------------------------------------------
Kent Gibson (1):
      gpiolib: cdev: clear debounce period if line set to output

Quanyang Wang (1):
      gpiolib: free device name on error path to fix kmemleak

Wolfram Sang (1):
      gpio: gpiolib: remove shadowed variable

 drivers/gpio/gpiolib-cdev.c |  2 ++
 drivers/gpio/gpiolib.c      | 12 +++++++++---
 2 files changed, 11 insertions(+), 3 deletions(-)

             reply	other threads:[~2021-02-03 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 13:08 Bartosz Golaszewski [this message]
2021-02-03 19:38 ` [GIT PULL] gpio: fixes for v5.11-rc7 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=20210203130857.17648-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --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