From: Baolin Wang <baolin.wang@spreadtrum.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Baolin Wang <baolin.wang@linaro.org>
Subject: Re: [PATCH v3 1/2] DT: pinctrl: Add binding documentation for Spreadtrum pin controller
Date: Mon, 12 Jun 2017 14:08:48 +0800 [thread overview]
Message-ID: <20170612060847.GB8566@spreadtrum.com> (raw)
In-Reply-To: <CACRpkdYzefkRNH9D0554Nzw_gJAUCMWgT15-k9zSaqg07x98FA@mail.gmail.com>
Hi Linus,
On 五, 6月 09, 2017 at 01:08:28下午 +0200, Linus Walleij wrote:
> On Tue, Jun 6, 2017 at 3:03 PM, Baolin Wang <baolin.wang@spreadtrum.com> wrote:
>
> > This patch adds the binding documentation for Spreadtrum SC9860 pin
> > controller device.
> >
> > Signed-off-by: Baolin Wang <baolin.wang@spreadtrum.com>
> > ---
> > Changes since v2:
> > - No updates.
>
> Same comments as v3, sorry for my slowness in review :(
It's okay and I understand you are so busy:)
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2017-06-12 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 13:03 [PATCH v3 1/2] DT: pinctrl: Add binding documentation for Spreadtrum pin controller Baolin Wang
2017-06-06 13:03 ` Baolin Wang
[not found] ` <359d62c1f2f7ef61c6160df9b60c1af4bfcea89a.1496753918.git.baolin.wang-lxIno14LUO0EEoCn2XhGlw@public.gmane.org>
2017-06-06 13:03 ` [PATCH v3 2/2] pinctrl: sprd: Add Spreadtrum pin control driver Baolin Wang
2017-06-06 13:03 ` Baolin Wang
2017-06-09 11:08 ` [PATCH v3 1/2] DT: pinctrl: Add binding documentation for Spreadtrum pin controller Linus Walleij
2017-06-12 6:08 ` Baolin Wang [this message]
2017-06-09 13:44 ` Rob Herring
2017-06-12 6:20 ` Baolin Wang
2017-06-12 6:20 ` Baolin Wang
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=20170612060847.GB8566@spreadtrum.com \
--to=baolin.wang@spreadtrum.com \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.