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>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: immutable branch between the GPIO and pinctrl trees for v6.8-rc1
Date: Fri,  8 Dec 2023 09:36:50 +0100	[thread overview]
Message-ID: <20231208083650.25015-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Linus, Andy,

Please pull the following changes into your trees for the next merge window.
These are the patches providing a safer alternative for gpiochip_is_requested()
before we rework the locking in GPIOLIB.

Bart

The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-remove-gpiochip_is_requested-for-v6.8-rc1

for you to fetch changes up to f8d05e276b45e3097dfddd628fa991ce69c05c99:

  gpiolib: remove gpiochip_is_requested() (2023-12-08 09:26:43 +0100)

----------------------------------------------------------------
gpio: remove gpiochip_is_requested()

- provide a safer alternative to gpiochip_is_requested()
- convert all existing users
- remove gpiochip_is_requested()

----------------------------------------------------------------
Bartosz Golaszewski (10):
      gpiolib: provide gpiochip_dup_line_label()
      gpio: wm831x: use gpiochip_dup_line_label()
      gpio: wm8994: use gpiochip_dup_line_label()
      gpio: stmpe: use gpiochip_dup_line_label()
      pinctrl: abx500: use gpiochip_dup_line_label()
      pinctrl: nomadik: use gpiochip_dup_line_label()
      pinctrl: baytrail: use gpiochip_dup_line_label()
      pinctrl: sppctl: use gpiochip_dup_line_label()
      gpiolib: use gpiochip_dup_line_label() in for_each helpers
      gpiolib: remove gpiochip_is_requested()

 drivers/gpio/gpio-stmpe.c                 |  6 ++++-
 drivers/gpio/gpio-wm831x.c                | 14 +++++++----
 drivers/gpio/gpio-wm8994.c                | 13 +++++++----
 drivers/gpio/gpiolib.c                    | 35 ++++++++++++++++-----------
 drivers/pinctrl/intel/pinctrl-baytrail.c  | 11 +++++----
 drivers/pinctrl/nomadik/pinctrl-abx500.c  |  9 +++++--
 drivers/pinctrl/nomadik/pinctrl-nomadik.c |  6 ++++-
 drivers/pinctrl/sunplus/sppctl.c          | 10 ++++----
 include/linux/gpio/driver.h               | 39 ++++++++++++++++++++++++-------
 9 files changed, 96 insertions(+), 47 deletions(-)

             reply	other threads:[~2023-12-08  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08  8:36 Bartosz Golaszewski [this message]
2023-12-11 23:46 ` [GIT PULL] gpio: immutable branch between the GPIO and pinctrl trees for v6.8-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=20231208083650.25015-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).