From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linux GPIO <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [GIT PULL] intel-gpio for 6.9-2
Date: Thu, 25 Apr 2024 14:55:55 +0300 [thread overview]
Message-ID: <ZipEyyjM955f7ABy@black.fi.intel.com> (raw)
Hi Linux GPIO maintainers,
One small fix for long-standing non-critical issue in Intel Tangier driver
for v6.9-rcX. The change was tested on Intel Edison platform along with the
Linux Next for a few weeks w/o issues reported. Please, pull.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit ace0ebe5c98d66889f19e0f30e2518d0c58d0e04:
gpio: crystalcove: Use -ENOTSUPP consistently (2024-04-05 20:12:39 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v6.9-2
for you to fetch changes up to 7d045025a24b6336d444d359bd4312f351d017f9:
gpio: tangier: Use correct type for the IRQ chip data (2024-04-12 23:41:05 +0300)
----------------------------------------------------------------
intel-gpio for v6.9-2
* Make data pointer dereference robust in Intel Tangier driver
The following is an automated git shortlog grouped by driver:
tangier:
- Use correct type for the IRQ chip data
----------------------------------------------------------------
Andy Shevchenko (1):
gpio: tangier: Use correct type for the IRQ chip data
drivers/gpio/gpio-tangier.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2024-04-25 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 11:55 Andy Shevchenko [this message]
2024-04-25 12:36 ` [GIT PULL] intel-gpio for 6.9-2 Bartosz Golaszewski
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=ZipEyyjM955f7ABy@black.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 read-only IMAP folder(s) and NNTP newsgroup(s).