From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
NeilBrown <neil@brown.name>, DENG Qingfang <dqfext@gmail.com>,
Sean Wang <sean.wang@mediatek.com>,
Mark Lee <Mark-MC.Lee@mediatek.com>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>,
erkin.bozoglu@xeront.com, linux-staging@lists.linux.dev,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mips: dts: ralink: add MT7621 SoC
Date: Tue, 15 Mar 2022 18:32:04 +0100 [thread overview]
Message-ID: <20220315173204.GA14220@alpha.franken.de> (raw)
In-Reply-To: <20220315160149.3617-1-arinc.unal@arinc9.com>
On Tue, Mar 15, 2022 at 07:01:50PM +0300, Arınç ÜNAL wrote:
> The MT7621 system-on-a-chip includes an 880 MHz MIPS1004Kc dual-core CPU,
> a 5-port 10/100/1000 switch/PHY and one RGMII.
>
> Add the devicetrees for GB-PC1 and GB-PC2 devices which use MT7621 SoC.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> Acked-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> v2: fix a tiny grammar mistake, add Sergio's acked-by.
>
> This patch does changes on top of commit dcd520af4eac ("staging:
> mt7621-dts: fix cpuintc and fixedregulator dtc warnings, fix xhci") which
> is currently applied on gregkh/staging.git staging-next branch.
>
> ---
> MAINTAINERS | 7 +++++++
> arch/mips/boot/dts/ralink/Makefile | 4 ++++
> .../mips/boot/dts/ralink/mt7621-gnubee-gb-pc1.dts | 0
> .../mips/boot/dts/ralink/mt7621-gnubee-gb-pc2.dts | 0
> .../mips/boot/dts/ralink}/mt7621.dtsi | 0
> arch/mips/ralink/Kconfig | 5 +++++
> drivers/staging/Kconfig | 2 --
> drivers/staging/Makefile | 1 -
> drivers/staging/mt7621-dts/Kconfig | 11 -----------
> drivers/staging/mt7621-dts/Makefile | 5 -----
> drivers/staging/mt7621-dts/TODO | 5 -----
> 11 files changed, 16 insertions(+), 24 deletions(-)
> rename drivers/staging/mt7621-dts/gbpc1.dts => arch/mips/boot/dts/ralink/mt7621-gnubee-gb-pc1.dts (100%)
> rename drivers/staging/mt7621-dts/gbpc2.dts => arch/mips/boot/dts/ralink/mt7621-gnubee-gb-pc2.dts (100%)
> rename {drivers/staging/mt7621-dts => arch/mips/boot/dts/ralink}/mt7621.dtsi (100%)
> delete mode 100644 drivers/staging/mt7621-dts/Kconfig
> delete mode 100644 drivers/staging/mt7621-dts/Makefile
> delete mode 100644 drivers/staging/mt7621-dts/TODO
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-03-15 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:01 [PATCH v2] mips: dts: ralink: add MT7621 SoC Arınç ÜNAL
2022-03-15 17:32 ` Thomas Bogendoerfer [this message]
2022-03-16 6:48 ` Sergio Paracuellos
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=20220315173204.GA14220@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=Mark-MC.Lee@mediatek.com \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luizluca@gmail.com \
--cc=neil@brown.name \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sergio.paracuellos@gmail.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