From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Doug Anderson <dianders@chromium.org>,
Chris Zhong <zyw@rock-chips.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Rockchip patch storm
Date: Tue, 28 Oct 2014 19:21:21 +0100 [thread overview]
Message-ID: <7147197.9KAMDIqD0H@diego> (raw)
In-Reply-To: <CACRpkdacdWa2FbntzxF1Ou1Mo1bemWxJpNBfQhSc3n19hsQPPw@mail.gmail.com>
Hi Linus
Am Dienstag, 28. Oktober 2014, 17:21:46 schrieb Linus Walleij:
> Hi guys,
>
> with all the rockchip patches and cross-review going on may I ask
> that you decide on a person to collect and send pull requests to me
> for the Rockchip patch stack?
>
> Preferably Heiko.
ok, I'll collect our pinctrl patches and send you a pull request
Heiko
prev parent reply other threads:[~2014-10-28 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 16:21 Rockchip patch storm Linus Walleij
2014-10-28 18:21 ` Heiko Stübner [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=7147197.9KAMDIqD0H@diego \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zyw@rock-chips.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).