linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, Kent Gibson <warthog618@gmail.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [GIT PULL] gpio: updates for v5.9 - part 2
Date: Sun, 12 Jul 2020 10:25:29 +0200	[thread overview]
Message-ID: <20200712082529.21023-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

Hi Linus,

please pull the following set of changes from Kent introducing a lot
of improvements to the character device code. These are non-controversial
changes before the V2 uAPI.

Best regards,
Bartosz

The following changes since commit 4672a4a9fbfe316e1153682b0790af6446255a50:

  Merge branch 'devel' into for-next (2020-07-09 17:06:28 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-updates-for-v5.9-part2

for you to fetch changes up to df51f402e3b15b00284309bd3016bb4536d2260c:

  tools: gpio: fix spurious close warning in gpio-event-mon (2020-07-12 10:22:01 +0200)

----------------------------------------------------------------
gpio updates for v5.9 - part 2

- several improvements and minor tweaks to the GPIO character device code

----------------------------------------------------------------
Kent Gibson (17):
      gpiolib: move gpiolib-sysfs function declarations into their own header
      gpiolib: cdev: sort includes
      gpiolib: cdev: minor indentation fixes
      gpiolib: cdev: refactor gpiohandle_flags_to_desc_flags
      gpiolib: cdev: rename 'filep' and 'filp' to 'file' to be consistent with other use
      gpiolib: cdev: rename numdescs to num_descs
      gpiolib: cdev: remove pointless decrement of i
      gpiolib: cdev: use blocking notifier call chain instead of atomic
      gpiolib: cdev: rename priv to cdev
      gpiolib: cdev: fix minor race in GET_LINEINFO_WATCH
      gpiolib: cdev: remove recalculation of offset
      gpiolib: cdev: refactor linehandle cleanup into linehandle_free
      gpiolib: cdev: refactor lineevent cleanup into lineevent_free
      gpio: uapi: fix misplaced comment line
      tools: gpio: fix spurious close warning in lsgpio
      tools: gpio: fix spurious close warning in gpio-utils
      tools: gpio: fix spurious close warning in gpio-event-mon

 drivers/gpio/gpiolib-cdev.c  | 385 ++++++++++++++++++++-----------------------
 drivers/gpio/gpiolib-sysfs.c |   1 +
 drivers/gpio/gpiolib-sysfs.h |  24 +++
 drivers/gpio/gpiolib.c       |  15 +-
 drivers/gpio/gpiolib.h       |  20 +--
 include/uapi/linux/gpio.h    |   2 +-
 tools/gpio/gpio-event-mon.c  |   3 +-
 tools/gpio/gpio-utils.c      |   4 +-
 tools/gpio/lsgpio.c          |   3 +-
 9 files changed, 217 insertions(+), 240 deletions(-)
 create mode 100644 drivers/gpio/gpiolib-sysfs.h

             reply	other threads:[~2020-07-12  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12  8:25 Bartosz Golaszewski [this message]
2020-07-13 21:21 ` [GIT PULL] gpio: updates for v5.9 - part 2 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=20200712082529.21023-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bgolaszewski@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=warthog618@gmail.com \
    /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).