From: Linus Walleij <linus.walleij@linaro.org>
To: Jianqun Xu <jay.xu@rock-chips.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"David Wu" <david.wu@rock-chips.com>,
"Kever Yang" <kever.yang@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH 0/2] pinctrl: rockchip: codingstyle for pinctrl-rockchip
Date: Sat, 12 Sep 2020 13:27:44 +0200 [thread overview]
Message-ID: <CACRpkdYGJsK4Ek8pDCeNMWt41dd2s--Lkxewh4Po4E-45UdwMg@mail.gmail.com> (raw)
In-Reply-To: <20200117081358.5772-1-jay.xu@rock-chips.com>
Jianqun, Heiko,
On Fri, Jan 17, 2020 at 9:14 AM Jianqun Xu <jay.xu@rock-chips.com> wrote:
> Do codingstyle for pinctrl-rockchip by spliting driver by SoC types.
>
> Convenienty for reviewing, the first patch only moving
> pinctrl-rockchip.c from driver/pinctrl to driver/pinctrl/rockchip/ .
>
> Jianqun Xu (2):
> pinctrl: rockchip: new rockchip dir for pinctrl-rockchip
> pinctrl: rockchip: split rockchip pinctrl driver by SoC type
Why were these patches never applied? Is it my fault?
I don't even have patch 2/2 in my mailbox, possibly it was
too big!
Heiko if you're OK with this change can Jianqun just send a
rebased version?
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-09-12 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 9:40 [PATCH] pinctrl/rockchip: splite soc data to separated driver Jianqun Xu
2020-01-10 16:19 ` kbuild test robot
2020-01-13 1:16 ` [PATCH v2] " Jianqun Xu
2020-01-15 12:51 ` Linus Walleij
2020-01-16 3:44 ` Kever Yang
2020-01-16 7:14 ` [PATCH v3] pinctrl: rockchip: split rockchip pinctrl driver by SoC type Jianqun Xu
2020-01-16 7:47 ` [PATCH v3 RESEND] " Jianqun Xu
2020-01-16 10:34 ` Robin Murphy
2020-01-17 8:13 ` [PATCH 0/2] pinctrl: rockchip: codingstyle for pinctrl-rockchip Jianqun Xu
2020-01-17 8:13 ` [PATCH 1/2] pinctrl: rockchip: new rockchip dir " Jianqun Xu
2020-01-17 8:13 ` [PATCH v4 2/2] pinctrl: rockchip: split rockchip pinctrl driver by SoC type Jianqun Xu
2020-02-15 11:11 ` Heiko Stuebner
2020-09-12 11:27 ` Linus Walleij [this message]
2020-09-12 12:02 ` [PATCH 0/2] pinctrl: rockchip: codingstyle for pinctrl-rockchip Heiko Stübner
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=CACRpkdYGJsK4Ek8pDCeNMWt41dd2s--Lkxewh4Po4E-45UdwMg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=david.wu@rock-chips.com \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).