From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: zhaoxiao <zhaoxiao@uniontech.com>
Cc: robh+dt@kernel.org, maoxiaochuan@loongson.cn,
jiaxun.yang@flygoat.com, zhangqing@loongson.cn,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] mips: dts: loongson: fix DTC unit name warnings
Date: Thu, 27 May 2021 13:42:03 +0200 [thread overview]
Message-ID: <20210527114203.GB9210@alpha.franken.de> (raw)
In-Reply-To: <cover.1621586643.git.zhaoxiao@uniontech.com>
On Fri, May 21, 2021 at 05:40:23PM +0800, zhaoxiao wrote:
> *** BLURB HERE ***
>
> zhaoxiao (5):
> mips: dts: loongson: fix DTC unit name warnings
> mips: dts: loongson: fix DTC unit name warnings
> mips: dts: loongson: fix DTC unit name warnings
> mips: dts: loongson: fix DTC unit name warnings
> mips: dts: loongson: fix DTC unit name warnings
>
> arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi | 2 +-
> arch/mips/boot/dts/loongson/loongson64g-package.dtsi | 4 ++--
> arch/mips/boot/dts/loongson/loongson64v_4core_virtio.dts | 2 +-
> arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 2 +-
> arch/mips/boot/dts/loongson/rs780e-pch.dtsi | 2 +-
> 5 files changed, 6 insertions(+), 6 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-05-27 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 9:40 [PATCH 0/5] mips: dts: loongson: fix DTC unit name warnings zhaoxiao
2021-05-21 9:40 ` [PATCH 1/5] " zhaoxiao
2021-05-24 6:07 ` zhaoxiao
2021-05-21 9:40 ` [PATCH 2/5] " zhaoxiao
2021-05-24 6:07 ` zhaoxiao
2021-05-24 6:37 ` Jiaxun Yang
2021-05-21 9:40 ` [PATCH 3/5] " zhaoxiao
2021-05-24 6:07 ` zhaoxiao
2021-05-21 9:40 ` [PATCH 4/5] " zhaoxiao
2021-05-24 6:07 ` zhaoxiao
2021-05-24 6:07 ` [PATCH 0/5] " zhaoxiao
2021-05-24 6:08 ` [PATCH 5/5] " zhaoxiao
2021-05-24 6:36 ` [PATCH 0/5] " Jiaxun Yang
2021-05-27 11:42 ` Thomas Bogendoerfer [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=20210527114203.GB9210@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maoxiaochuan@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=zhangqing@loongson.cn \
--cc=zhaoxiao@uniontech.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 read-only IMAP folder(s) and NNTP newsgroup(s).