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: updates for v5.7 part2
Date: Mon, 2 Mar 2020 09:11:42 +0100 [thread overview]
Message-ID: <20200302081142.8599-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Linus,
this is the second batch of updates for v5.7. It contains two minor tweaks
to core gpiolib and two fixes for the line watch/unwatch ioctl().
The following changes since commit 869233f81337bfb33c79f1e7539147d52c0ba383:
gpiolib: Optimize gpiochip_remove() when check for requested line (2020-02-28 23:58:56 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-updates-for-v5.7-part2
for you to fetch changes up to 1931479788c5e3c0396a0bde3606e517c64b9f95:
gpiolib: fix bitmap operations related to line event watching (2020-03-02 08:52:55 +0100)
----------------------------------------------------------------
gpio updates for v5.7 part 2
- replace z zero-length array with flexible-array member in gpio-uniphier
- make naming of variables consistent in uapi line event code
- fix the behavior of line watch/unwatch ioctl()
----------------------------------------------------------------
Andy Shevchenko (1):
gpiolib: Rename 'event' to 'ge' to be consistent with other use
Bartosz Golaszewski (1):
gpiolib: fix bitmap operations related to line event watching
Gustavo A. R. Silva (1):
gpio: uniphier: Replace zero-length array with flexible-array member
Kent Gibson (1):
gpiolib: fix unwatch ioctl()
drivers/gpio/gpio-uniphier.c | 2 +-
drivers/gpio/gpiolib.c | 18 +++++++++---------
2 files changed, 10 insertions(+), 10 deletions(-)
next reply other threads:[~2020-03-02 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:11 Bartosz Golaszewski [this message]
2020-03-03 12:35 ` [GIT PULL] gpio: updates for v5.7 part2 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=20200302081142.8599-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.