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.4-rc8
Date: Wed, 13 Nov 2019 16:30:24 +0100	[thread overview]
Message-ID: <20191113153024.18507-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

Hi Linus,

this is probably my last batch of fixes for this release. Please pull.

The following changes since commit 31f4f5b495a62c9a8b15b1c3581acd5efeb9af8c:

  Linux 5.4-rc7 (2019-11-10 16:17:15 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 0161a94e2d1c713bd34d72bc0239d87c31747bf7:

  tools: gpio: Correctly add make dependencies for gpio_utils (2019-11-13 13:46:04 +0100)

----------------------------------------------------------------
gpio fixes for v5.4-rc8

- fix debounce times in max776520 and bd70528
- fix parallel build of gpio tools

----------------------------------------------------------------
Laura Abbott (1):
      tools: gpio: Correctly add make dependencies for gpio_utils

Thierry Reding (2):
      gpio: max77620: Fixup debounce delays
      gpio: bd70528: Use correct unit for debounce times

 drivers/gpio/gpio-bd70528.c  |  6 +++---
 drivers/gpio/gpio-max77620.c |  6 +++---
 tools/gpio/Build             |  1 +
 tools/gpio/Makefile          | 10 +++++++---
 4 files changed, 14 insertions(+), 9 deletions(-)

             reply	other threads:[~2019-11-13 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 15:30 Bartosz Golaszewski [this message]
2019-11-13 21:58 ` [GIT PULL] gpio: fixes for v5.4-rc8 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=20191113153024.18507-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