From: Linus Walleij <linus.walleij@linaro.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Andy Yan <andy.yan@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk <linux-clk@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Shawn Lin <shawn.lin@rock-chips.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/7] Rename RK1108 to RV1108
Date: Tue, 14 Mar 2017 14:36:24 +0100 [thread overview]
Message-ID: <CACRpkdbuX7f58S_sTBMVEusX2g1iJ4T-cw9efJLFSYb8fV=EDA@mail.gmail.com> (raw)
In-Reply-To: <4369285.zq7cJYMXhu@phil>
On Thu, Feb 23, 2017 at 4:00 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> Am Donnerstag, 23. Februar 2017, 11:15:56 CET schrieb Linus Walleij:
>> Nobody gets hurt. Just rename everything to avoid confusion.
>> Just my €0.01.
>>
>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>
>> Tell me if I can merge a subset of the patches to the pinctrl tree.
>
> I did provide Reviewed-bys for them, so you should be able to merge the
> pinctrl patches (4+5) at your convenience :-)
They are conflicting right now, but I will merge it when I get a v4.11-rc1
based series.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-03-14 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 10:59 [PATCH 0/7] Rename RK1108 to RV1108 Andy Yan
2017-02-13 11:07 ` [PATCH 5/7] pinctrl: rockchip: rename " Andy Yan
2017-02-22 18:34 ` Heiko Stuebner
2017-02-13 12:51 ` [PATCH 0/7] Rename " Heiko Stuebner
2017-02-14 0:44 ` Andy Yan
2017-02-23 10:15 ` Linus Walleij
[not found] ` <CACRpkdbNbGvwUq3uLgekimOwzBZCXf37JW9LCCqLm1so=CMNrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-23 15:00 ` Heiko Stuebner
2017-03-14 13:36 ` Linus Walleij [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='CACRpkdbuX7f58S_sTBMVEusX2g1iJ4T-cw9efJLFSYb8fV=EDA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@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).