From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: Intel GPIO / pin control repositories for next
Date: Thu, 15 Aug 2019 10:06:14 +0200 [thread overview]
Message-ID: <CACRpkdYhF3GYjqp69z=uMuTuRGkDdnRp4Dn=d1rtYR79XFp0YA@mail.gmail.com> (raw)
In-Reply-To: <20190813135053.GA30120@smile.fi.intel.com>
On Tue, Aug 13, 2019 at 3:50 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> Can you, please, include the following repositories for your linux-next bunch
> for getting better coverage?
Excellent initiative Andy!
When it feels the branches are solid just toss them over to me.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-08-15 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 13:50 Intel GPIO / pin control repositories for next Andy Shevchenko
2019-08-15 8:06 ` Linus Walleij [this message]
2019-08-13 14:04 Andy Shevchenko
2019-08-13 14:20 ` Stephen Rothwell
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='CACRpkdYhF3GYjqp69z=uMuTuRGkDdnRp4Dn=d1rtYR79XFp0YA@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).