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.17-rc6
Date: Fri, 25 Feb 2022 21:42:02 +0100 [thread overview]
Message-ID: <20220225204202.53415-1-brgl@bgdev.pl> (raw)
Linus,
Please pull the following two fixes for the next release cycle.
Best Regards,
Bartosz Golaszewski
The following changes since commit 754e0b0e35608ed5206d6a67a791563c631cec07:
Linux 5.17-rc4 (2022-02-13 12:13:30 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v5.17-rc6
for you to fetch changes up to ae42f9288846353982e2eab181fb41e7fd8bf60f:
gpio: Return EPROBE_DEFER if gc->to_irq is NULL (2022-02-23 22:30:56 +0100)
----------------------------------------------------------------
gpio: fixes for v5.17-rc6
- fix an bug generating spurious interrupts in gpio-rockchip
- fix a race condition in gpiod_to_irq() called by GPIO consumers
----------------------------------------------------------------
Samuel Holland (1):
gpio: rockchip: Reset int_bothedge when changing trigger
Shreeya Patel (1):
gpio: Return EPROBE_DEFER if gc->to_irq is NULL
drivers/gpio/gpio-rockchip.c | 56 +++++++++++++++++++++++---------------------
drivers/gpio/gpiolib.c | 10 ++++++++
2 files changed, 39 insertions(+), 27 deletions(-)
next reply other threads:[~2022-02-25 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 20:42 Bartosz Golaszewski [this message]
2022-02-25 21:18 ` [GIT PULL] gpio: fixes for v5.17-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=20220225204202.53415-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