From: icenowy@aosc.io
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] Last step to working Allwinner R40 pinctrl
Date: Sun, 30 Jul 2017 13:26:46 +0800 [thread overview]
Message-ID: <57922ac75d55aef45ae8d09df76418ea@aosc.io> (raw)
In-Reply-To: <20170722025054.32645-1-icenowy@aosc.io>
在 2017-07-22 10:50，Icenowy Zheng 写道：
> This patchset contains only two patches.
>
> The first one is a minor fix for the A10 pinctrl driver, add a function
> of a pin, which used to be missing in A10/A20 pinctrl driver. Thanks
> for
> Chen-Yu for discovering it when reviewing my R40 pinctrl patchset.
>
> The second one is the real R40 pinctrl part, with fixes suggested by
> Chen-Yu and Maxime.
>
> Icenowy Zheng (2):
> pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
> pinctrl: sunxi: add support of R40 to A10 pinctrl driver
Ping...
Can anyone process this patchset?
>
> drivers/pinctrl/sunxi/Kconfig | 2 +-
> drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c | 274
> +++++++++++++++++++++---------
> 2 files changed, 197 insertions(+), 79 deletions(-)
next prev parent reply other threads:[~2017-07-30 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 2:50 [PATCH v3 0/2] Last step to working Allwinner R40 pinctrl Icenowy Zheng
[not found] ` <20170722025054.32645-1-icenowy-h8G6r0blFSE@public.gmane.org>
2017-07-22 2:50 ` [PATCH v3 1/2] pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver Icenowy Zheng
2017-07-31 13:53 ` Linus Walleij
2017-07-22 2:50 ` [PATCH v3 2/2] pinctrl: sunxi: add support of R40 to A10 " Icenowy Zheng
[not found] ` <20170722025054.32645-3-icenowy-h8G6r0blFSE@public.gmane.org>
2017-07-31 13:55 ` Linus Walleij
2017-07-30 5:26 ` icenowy [this message]
2017-07-31 13:52 ` [PATCH v3 0/2] Last step to working Allwinner R40 pinctrl 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=57922ac75d55aef45ae8d09df76418ea@aosc.io \
--to=icenowy@aosc.io \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.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 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).