From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux pin control <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-pinctrl for 5.6-1
Date: Fri, 24 Jan 2020 12:57:35 +0200 [thread overview]
Message-ID: <20200124105735.GC32742@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdZh4Cy83BPfdgcXR6idf7KCr15VD0YkR-7CcDxV=HZgaQ@mail.gmail.com>
On Thu, Jan 23, 2020 at 03:45:14PM +0100, Linus Walleij wrote:
> On Mon, Jan 20, 2020 at 11:10 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Intel pin control drivers update for v5.6 (next release cycle).
...
> Pulled this into my "devel" branch for v5.6.
Thanks!
How long usually does it take to see in linux-next?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-01-24 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 10:09 [GIT PULL] intel-pinctrl for 5.6-1 Andy Shevchenko
2020-01-23 14:45 ` Linus Walleij
2020-01-24 10:57 ` Andy Shevchenko [this message]
2020-01-24 13:02 ` Linus Walleij
2020-01-24 13:21 ` Andy Shevchenko
2020-01-24 13:33 ` 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=20200124105735.GC32742@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--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