From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] GPIO fixes for v4.12 last one
Date: Sat, 1 Jul 2017 14:18:11 +0200 [thread overview]
Message-ID: <CACRpkdYmdUi32R1Cv120DvqF1DJO2aWp7gNbt9co4Sb+H+D6CA@mail.gmail.com> (raw)
Hi Linus,
just when I thought everything was setting down nicely last minute
fixes appear. Like sunspots.
Please pull it in, I would have sent earlier this week but the 0day
builder was unresponsive so I wanted it to land in linux-next
first.
(If it's too late, it's too late, I just fold it into the v4.13 window and
tag for stable then, no big deal.)
Yours,
Linus Walleij
The following changes since commit c0bc126f97fb929b3ae02c1c62322645d70eb408:
Linux 4.12-rc7 (2017-06-25 18:30:05 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v4.12-4
for you to fetch changes up to c06632ea054c49510efacb42c52aab693c45b7ba:
gpio: acpi: Skip _AEI entries without a handler rather then aborting
the scan (2017-06-29 14:55:08 +0200)
----------------------------------------------------------------
Last minute fixes for GPIO:
- Fix another ACPI problem with broken BIOSes.
- Filter out the GPIO right events, making a very user-visible bug
go away.
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpiolib: fix filtering out unwanted events
Hans de Goede (1):
gpio: acpi: Skip _AEI entries without a handler rather then
aborting the scan
drivers/gpio/gpiolib-acpi.c | 2 +-
drivers/gpio/gpiolib.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
reply other threads:[~2017-07-01 12:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACRpkdYmdUi32R1Cv120DvqF1DJO2aWp7gNbt9co4Sb+H+D6CA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=hdegoede@redhat.com \
--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).