From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Xuefeng Li <lixuefeng@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] MIPS: Clean up device_tree_init()
Date: Mon, 14 Mar 2022 15:50:49 +0100 [thread overview]
Message-ID: <20220314145049.GA13438@alpha.franken.de> (raw)
In-Reply-To: <1646895012-3143-1-git-send-email-yangtiezhu@loongson.cn>
On Thu, Mar 10, 2022 at 02:50:09PM +0800, Tiezhu Yang wrote:
> Tiezhu Yang (3):
> MIPS: Remove redundant check in device_tree_init()
> MIPS: Remove redundant definitions of device_tree_init()
> MIPS: Fix wrong comments in asm/prom.h
>
> arch/mips/ath79/setup.c | 5 -----
> arch/mips/include/asm/prom.h | 4 ++--
> arch/mips/kernel/prom.c | 5 +++++
> arch/mips/lantiq/prom.c | 5 -----
> arch/mips/loongson64/setup.c | 8 --------
> arch/mips/mti-malta/Makefile | 1 -
> arch/mips/mti-malta/malta-dt.c | 15 ---------------
> arch/mips/pic32/pic32mzda/init.c | 8 --------
> arch/mips/ralink/of.c | 5 -----
> 9 files changed, 7 insertions(+), 49 deletions(-)
> delete mode 100644 arch/mips/mti-malta/malta-dt.c
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:[~2022-03-14 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 6:50 Tiezhu Yang
2022-03-10 6:50 ` [PATCH 1/3] MIPS: Remove redundant check in device_tree_init() Tiezhu Yang
2022-03-10 6:50 ` [PATCH 2/3] MIPS: Remove redundant definitions of device_tree_init() Tiezhu Yang
2022-03-10 6:50 ` [PATCH 3/3] MIPS: Fix wrong comments in asm/prom.h Tiezhu Yang
2022-03-14 14:50 ` 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=20220314145049.GA13438@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®