From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: linux-mips@vger.kernel.org, Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>,
Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/4] MIPS: Loongson64: Fix machine naming
Date: Thu, 16 Jul 2020 12:00:45 +0200 [thread overview]
Message-ID: <20200716100045.GH8455@alpha.franken.de> (raw)
In-Reply-To: <1594294424-26218-1-git-send-email-chenhc@lemote.com>
On Thu, Jul 09, 2020 at 07:33:41PM +0800, Huacai Chen wrote:
> >From previous commits, the machine names with "loongson3-" prefix have
> renamed to "loongson64c-" prefix in documents, but the .dts files have
> not been updated as well. So fix it.
>
> Signed-off-by: Huacai Chen <chenhc@lemote.com>
> ---
> arch/mips/boot/dts/loongson/loongson64c_4core_rs780e.dts | 2 +-
> arch/mips/boot/dts/loongson/loongson64c_8core_rs780e.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
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:[~2020-07-16 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 11:33 [PATCH 1/4] MIPS: Loongson64: Fix machine naming Huacai Chen
2020-07-09 11:33 ` [PATCH 2/4] MIPS: Loongson64: DeviceTree for LS7A PCH Huacai Chen
2020-07-14 7:26 ` Tiezhu Yang
2020-07-16 10:01 ` Thomas Bogendoerfer
2020-07-09 11:33 ` [PATCH 3/4] MIPS: Loongson64: Load LS7A dtbs Huacai Chen
2020-07-14 7:27 ` Tiezhu Yang
2020-07-16 10:01 ` Thomas Bogendoerfer
2020-07-09 11:33 ` [PATCH 4/4] MIPS: Loongson64: Reserve legacy MMIO space according to bridge type Huacai Chen
2020-07-14 7:27 ` Tiezhu Yang
2020-07-16 10:00 ` Thomas Bogendoerfer
2020-07-16 11:10 ` Huacai Chen
2020-07-16 12:04 ` Thomas Bogendoerfer
2020-07-17 1:33 ` Huacai Chen
2020-07-14 7:25 ` [PATCH 1/4] MIPS: Loongson64: Fix machine naming Tiezhu Yang
2020-07-16 10:00 ` 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=20200716100045.GH8455@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=chenhuacai@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.