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-rc6
Date: Fri, 8 Jul 2022 17:48:32 +0200 [thread overview]
Message-ID: <20220708154832.67452-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following fixes from the GPIO subsystem.
Best Regards,
Bartosz Golaszewski
The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:
Linux 5.19-rc4 (2022-06-26 14:22:10 -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-rc6
for you to fetch changes up to c8e27a4a5136e7230f9e4ffcf132705bf56864cc:
gpiolib: cdev: fix null pointer dereference in linereq_free() (2022-07-07 12:18:18 +0200)
----------------------------------------------------------------
gpio fixes for v5.19-rc6
- fix a build error in gpio-vf610
- fix a null-pointer dereference in the GPIO character device code
----------------------------------------------------------------
Kent Gibson (1):
gpiolib: cdev: fix null pointer dereference in linereq_free()
Leon Romanovsky (1):
gpio: vf610: fix compilation error
drivers/gpio/gpio-vf610.c | 1 +
drivers/gpio/gpiolib-cdev.c | 7 ++++---
2 files changed, 5 insertions(+), 3 deletions(-)
next reply other threads:[~2022-07-08 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 15:48 Bartosz Golaszewski [this message]
2022-07-08 20:32 ` [GIT PULL] gpio: fixes for v5.19-rc6 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=20220708154832.67452-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