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: fixes for v5.19-rc8
Date: Fri, 22 Jul 2022 17:33:44 +0200 [thread overview]
Message-ID: <20220722153344.151561-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following set of fixes for the upcoming rc.
Thanks!
Bartosz Golaszewski
The following changes since commit ff6992735ade75aae3e35d16b17da1008d753d28:
Linux 5.19-rc7 (2022-07-17 13:30:22 -0700)
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-rc8
for you to fetch changes up to 32c094a09d5829ad9b02cdf667569aefa8de0ea6:
gpio: gpio-xilinx: Fix integer overflow (2022-07-22 09:17:03 +0200)
----------------------------------------------------------------
gpio fixes for v5.19-rc8
- fix several regmap usage issues in gpio-pca953x
- fix out-of-tree build for GPIO selftests
- fix integer overflow in gpio-xilinx
----------------------------------------------------------------
Haibo Chen (3):
gpio: pca953x: only use single read/write for No AI mode
gpio: pca953x: use the correct range when do regmap sync
gpio: pca953x: use the correct register address when regcache sync during init
Kent Gibson (1):
selftests: gpio: fix include path to kernel headers for out of tree builds
Srinivas Neeli (1):
gpio: gpio-xilinx: Fix integer overflow
drivers/gpio/gpio-pca953x.c | 22 ++++++++++++++--------
drivers/gpio/gpio-xilinx.c | 2 +-
tools/testing/selftests/gpio/Makefile | 2 +-
3 files changed, 16 insertions(+), 10 deletions(-)
next reply other threads:[~2022-07-22 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 15:33 Bartosz Golaszewski [this message]
2022-07-22 20:07 ` 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=20220722153344.151561-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
all inboxes | Powered by JetHome®