linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] late GPIO fixes for v5.9
Date: Fri, 9 Oct 2020 10:20:48 +0200	[thread overview]
Message-ID: <CACRpkdYLfx9qRb1hHi=u+hLxzYE=0aku+_8-KwYocHmPowMZbQ@mail.gmail.com> (raw)

Hi Linus,

some two late GPIO fixes: one IRQ issue and one compilation
issue for UML.

Please pull them in!

Yours,
Linus Walleij

The following changes since commit 549738f15da0e5a00275977623be199fbbf7df50:

  Linux 5.9-rc8 (2020-10-04 16:04:34 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v5.9-3

for you to fetch changes up to 8b81edd80baf12d64420daff1759380aa9a14998:

  gpio: pca953x: Survive spurious interrupts (2020-10-07 11:47:41 +0200)

----------------------------------------------------------------
Some late fixes for the v5.9 kernel:

- Fix a compilation issue with User Mode Linux.

- Handle spurious interrupts properly in the PCA953x driver.

----------------------------------------------------------------
Andy Shevchenko (1):
      gpiolib: Disable compat ->read() code in UML case

Marc Zyngier (1):
      gpio: pca953x: Survive spurious interrupts

 drivers/gpio/gpio-pca953x.c | 17 +++++++++++++++--
 drivers/gpio/gpiolib-cdev.c |  2 +-
 2 files changed, 16 insertions(+), 3 deletions(-)

             reply	other threads:[~2020-10-09  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  8:20 Linus Walleij [this message]
2020-10-09 19:31 ` [GIT PULL] late GPIO fixes for v5.9 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-10-02  9:31 Linus Walleij
2020-10-02 17: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='CACRpkdYLfx9qRb1hHi=u+hLxzYE=0aku+_8-KwYocHmPowMZbQ@mail.gmail.com' \
    --to=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;
as well as URLs for NNTP newsgroup(s).