From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linux pin control <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-pinctrl for 5.5-2
Date: Fri, 13 Dec 2019 11:01:54 +0100 [thread overview]
Message-ID: <CACRpkdZYhw9tEYmQjZaOLanUrsLzHK-FE=nJtc+GKc0rH88mEg@mail.gmail.com> (raw)
In-Reply-To: <20191209122247.GA85209@black.fi.intel.com>
On Mon, Dec 9, 2019 at 1:22 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> This is material for v5.5-rc2.
>
> There are two fixes for BayTrail and the rest of conversion to pass IRQ chip
> along with GPIO one. The latter is a part 2 of the merge which has been delayed
> to -rc1 for dependency reasons. It has been hanging for few weeks in Linux next.
Pulled into my pinctrl "fixes" branch, thanks!
Yours,
Linus Walleij
prev parent reply other threads:[~2019-12-13 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:22 [GIT PULL] intel-pinctrl for 5.5-2 Andy Shevchenko
2019-12-13 10:01 ` Linus Walleij [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='CACRpkdZYhw9tEYmQjZaOLanUrsLzHK-FE=nJtc+GKc0rH88mEg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@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).