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>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] GPIO fixes for v4.16
Date: Sun, 11 Mar 2018 11:06:22 +0100	[thread overview]
Message-ID: <CACRpkdZvwWmh7NqcoM9bgTxnLECv5thLavyCAS7jPv87DF0ZTA@mail.gmail.com> (raw)

Hi Linus,

here is a singular fix for v4.16 and the Renesas RCAR driver.

Please pull it in!

Yours,
Linus Walleij

The following changes since commit 661e50bc853209e41a5c14a290ca4decc43cbfd1:

  Linux 4.16-rc4 (2018-03-04 14:54:11 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
tags/gpio-v4.16-3

for you to fetch changes up to 9ac79ba9c77d8595157bbdc4327919f8ee062426:

  gpio: rcar: Use wakeup_path i.s.o. explicit clock handling
(2018-03-05 09:01:21 +0100)

----------------------------------------------------------------
This is a single GPIO fix for the v4.16 series affecting the
Renesas driver, and fixes wakeup from external stuff.

----------------------------------------------------------------
Geert Uytterhoeven (1):
      gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

 drivers/gpio/gpio-rcar.c | 38 ++++++++++++++++----------------------
 1 file changed, 16 insertions(+), 22 deletions(-)

             reply	other threads:[~2018-03-11 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 10:06 Linus Walleij [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-26  9:36 [GIT PULL] GPIO fixes for v4.16 Linus Walleij
2018-02-26  9:46 ` Maxime Ripard
2018-02-26  9:54   ` Linus Walleij

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=CACRpkdZvwWmh7NqcoM9bgTxnLECv5thLavyCAS7jPv87DF0ZTA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=geert+renesas@glider.be \
    --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).