From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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: updates for v5.19-rc1
Date: Fri, 3 Jun 2022 16:28:12 +0200 [thread overview]
Message-ID: <20220603142812.66869-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following set of fixes for the upcoming rc.
Best regards,
Bartosz Golaszewski
The following changes since commit 4b0986a3613c92f4ec1bdc7f60ec66fea135991f:
Linux 5.18 (2022-05-22 09:52:31 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.19-rc1
for you to fetch changes up to 7bb8a0cf49d5fede1104afdcb43bd2f8a1df3253:
gpio: adp5588: Remove support for platform setup and teardown callbacks (2022-06-02 09:17:38 +0200)
----------------------------------------------------------------
gpio updates for v5.19-rc1
- use the correct register for regcache sync in gpio-pca953x
- remove unused and potentially harmful code from gpio-adp5588
- MAINTAINERS update
----------------------------------------------------------------
Andy Shevchenko (2):
MAINTAINERS: Update GPIO ACPI library to Supported
MAINTAINERS: Update Intel GPIO (PMIC and PCH) to Supported
Haibo Chen (1):
gpio: pca953x: use the correct register address to do regcache sync
Uwe Kleine-König (1):
gpio: adp5588: Remove support for platform setup and teardown callbacks
MAINTAINERS | 6 +++---
drivers/gpio/gpio-adp5588.c | 19 -------------------
drivers/gpio/gpio-pca953x.c | 19 +++++++++++--------
3 files changed, 14 insertions(+), 30 deletions(-)
next reply other threads:[~2022-06-03 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 14:28 Bartosz Golaszewski [this message]
2022-06-04 3:05 ` [GIT PULL] gpio: updates for v5.19-rc1 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=20220603142812.66869-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).