linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [GIT PULL] pin control fixes for v4.19
Date: Fri, 21 Sep 2018 10:03:09 -0700	[thread overview]
Message-ID: <CACRpkdaTsM-VV7ck1E8Q_Fv+9NSQ7a8mQp_WAyBMvZjGkrYeLg@mail.gmail.com> (raw)

Hi Greg,

here are some two fixes for pin contol for v4.19.

Please pull them in for the current HEAD.

Yours,
Linus Walleij

The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:

  Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v4.19-3

for you to fetch changes up to 96147db1e1dff83679e71ac92193cbcab761a14c:

  pinctrl: intel: Do pin translation in other GPIO operations as well
(2018-09-20 08:21:52 -0700)

----------------------------------------------------------------
Pin control fixes for v4.19:

- Two fixes for the Intel pin controllers than cause
  problems on laptops.

----------------------------------------------------------------
Mika Westerberg (1):
      pinctrl: intel: Do pin translation in other GPIO operations as well

Simon Detheridge (1):
      pinctrl: cannonlake: Fix gpio base for GPP-E

 drivers/pinctrl/intel/pinctrl-cannonlake.c |   2 +-
 drivers/pinctrl/intel/pinctrl-intel.c      | 111 ++++++++++++++++-------------
 2 files changed, 64 insertions(+), 49 deletions(-)

             reply	other threads:[~2018-09-21 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-21 17:03 Linus Walleij [this message]
2018-09-21 18:48 ` [GIT PULL] pin control fixes for v4.19 Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2018-09-13 12:13 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=CACRpkdaTsM-VV7ck1E8Q_Fv+9NSQ7a8mQp_WAyBMvZjGkrYeLg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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).