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.15
Date: Fri, 29 Oct 2021 22:45:50 +0200 [thread overview]
Message-ID: <20211029204550.24882-1-brgl@bgdev.pl> (raw)
Linus,
This is the last batch of fixes for the GPIO subsystem. Nothing worth
noting, just minor driver fixes.
Please pull.
Best Regards,
Bartosz Golaszewski
The following changes since commit 6fda593f3082ef1aa783ac13e89f673fd69a2cb6:
gpio: mockup: Convert to use software nodes (2021-10-06 13:04:04 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v5.15
for you to fetch changes up to c0eee6fbfa2b3377f1efed10dad539abeb7312aa:
gpio: mlxbf2.c: Add check for bgpio_init failure (2021-10-25 10:15:05 +0200)
----------------------------------------------------------------
gpio fixes for v5.15
- fix the return value check when parsing the ngpios property in gpio-xgs-iproc
- check the return value of bgpio_init() in gpio-mlxbf2
----------------------------------------------------------------
Asmaa Mnebhi (1):
gpio: mlxbf2.c: Add check for bgpio_init failure
Jonas Gorski (1):
gpio: xgs-iproc: fix parsing of ngpios property
drivers/gpio/gpio-mlxbf2.c | 5 +++++
drivers/gpio/gpio-xgs-iproc.c | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
next reply other threads:[~2021-10-29 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 20:45 Bartosz Golaszewski [this message]
2021-10-30 0:37 ` [GIT PULL] gpio: fixes for v5.15 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=20211029204550.24882-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 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.