From: Linus Walleij <linus.walleij@linaro.org>
To: Zhou Yanjie <zhouyanjie@zoho.com>
Cc: linux-mips@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Paul Burton <paul.burton@mips.com>,
Paul Burton <paulburton@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Paul Cercueil <paul@crapouillou.net>
Subject: Re: Fix bugs in X1000/X1500 and add X1830 pinctrl driver v4.
Date: Thu, 28 Nov 2019 10:20:00 +0100 [thread overview]
Message-ID: <CACRpkdYZfwXTfdiVtZgbTy9U7VxCE471N2ysWF7Vo7Fasn0Uxw@mail.gmail.com> (raw)
In-Reply-To: <1574533806-112333-1-git-send-email-zhouyanjie@zoho.com>
On Sat, Nov 23, 2019 at 7:30 PM Zhou Yanjie <zhouyanjie@zoho.com> wrote:
> v3->v4:
> 1.Use local variables to streamline code.
> 2.Prevents processors older than X1830 from being
> configured in HiZ mode.
I see the buildrobot is complaining about patch 4.
Please wait for v5.5-rc1 and rebase on that and resend
after the merge window.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-11-28 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 18:30 Fix bugs in X1000/X1500 and add X1830 pinctrl driver v4 Zhou Yanjie
2019-11-23 18:30 ` [PATCH RESEND v4 1/4] pinctrl: Ingenic: Fix bugs in X1000 and X1500 Zhou Yanjie
2019-11-23 18:30 ` [PATCH RESEND v4 2/4] pinctrl: Ingenic: Add missing parts for " Zhou Yanjie
2019-11-23 18:30 ` [PATCH RESEND v4 3/4] dt-bindings: pinctrl: Add bindings for Ingenic X1830 Zhou Yanjie
2019-11-23 18:30 ` [PATCH RESEND v4 4/4] pinctrl: Ingenic: Add pinctrl driver for X1830 Zhou Yanjie
2019-11-25 1:35 ` kbuild test robot
2019-11-28 9:20 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-17 18:14 Fix bugs in X1000/X1500 and add X1830 pinctrl driver v4 Zhou Yanjie
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=CACRpkdYZfwXTfdiVtZgbTy9U7VxCE471N2ysWF7Vo7Fasn0Uxw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul.burton@mips.com \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=zhouyanjie@zoho.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).