From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Shiji Yang <yangshiji66@outlook.com>
Cc: linux-mips@vger.kernel.org, john@phrozen.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] mips: ralink: introduce commonly used remap node function
Date: Wed, 21 Jun 2023 16:08:22 +0200 [thread overview]
Message-ID: <20230621140822.GC7206@alpha.franken.de> (raw)
In-Reply-To: <OSYP286MB03120BABB25900E113ED42B7BC5CA@OSYP286MB0312.JPNP286.PROD.OUTLOOK.COM>
On Tue, Jun 20, 2023 at 07:44:32PM +0800, Shiji Yang wrote:
> The ralink_of_remap() function is repeated several times on SoC specific
> source files. They have the same structure, but just differ in compatible
> strings. In order to make commonly use of these codes, this patch
> introduces a newly designed mtmips_of_remap_node() function to match and
> remap all supported system controller and memory controller nodes.
>
> Build and run tested on MT7620 and MT7628.
>
> Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
> ---
> arch/mips/ralink/common.h | 2 --
> arch/mips/ralink/mt7620.c | 9 ---------
> arch/mips/ralink/mt7621.c | 9 ---------
> arch/mips/ralink/of.c | 42 ++++++++++++++++++++++++++++++++-------
> arch/mips/ralink/rt288x.c | 9 ---------
> arch/mips/ralink/rt305x.c | 9 ---------
> arch/mips/ralink/rt3883.c | 9 ---------
> 7 files changed, 35 insertions(+), 54 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:[~2023-06-21 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:44 [PATCH] mips: ralink: introduce commonly used remap node function Shiji Yang
2023-06-20 12:55 ` Sergio Paracuellos
2023-06-21 1:09 ` Shiji Yang
2023-06-21 14:08 ` 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=20230621140822.GC7206@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=yangshiji66@outlook.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).