From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [GIT PULL] pin control fix for v4.19
Date: Fri, 12 Oct 2018 13:12:02 +0200 [thread overview]
Message-ID: <20181012111202.GD6536@kroah.com> (raw)
In-Reply-To: <CACRpkdYaWwrwYvOK9PoFE7GvyAZxVA5JqPbCRSpLHLVcQubp6w@mail.gmail.com>
On Fri, Oct 12, 2018 at 10:30:18AM +0200, Linus Walleij wrote:
> Hi Greg,
>
> Here is a last minute pin control fix for the v4.19 series.
>
> Please pull it in. It fixes interrupts on the MCP23s08.
>
> Yours,
> Linus Walleij
>
>
> The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21:
>
> Linux 4.19-rc7 (2018-10-07 17:26:02 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
> tags/pinctrl-v4.19-5
Now merged, thanks.
greg k-h
prev parent reply other threads:[~2018-10-12 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 8:30 [GIT PULL] pin control fix for v4.19 Linus Walleij
2018-10-12 11:12 ` Greg KH [this message]
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=20181012111202.GD6536@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
/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