From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mips: dts: ralink: mt7621: add mdio label to mdio-bus
Date: Wed, 27 Apr 2022 10:59:14 +0200 [thread overview]
Message-ID: <20220427085914.GA8404@alpha.franken.de> (raw)
In-Reply-To: <20220411112049.18001-1-arinc.unal@arinc9.com>
On Mon, Apr 11, 2022 at 02:20:47PM +0300, Arınç ÜNAL wrote:
> Add mdio label to the mdio-bus node to easily refer to it.
>
> Use the newly created label on the GB-PC2 devicetree.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> Reviewed-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> v2: add "ralink:" to the commit summary
>
> ---
> .../boot/dts/ralink/mt7621-gnubee-gb-pc2.dts | 18 ++++++++----------
> arch/mips/boot/dts/ralink/mt7621.dtsi | 2 +-
> 2 files changed, 9 insertions(+), 11 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:[~2022-04-27 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 11:20 [PATCH v2 1/3] mips: dts: ralink: mt7621: add mdio label to mdio-bus Arınç ÜNAL
2022-04-11 11:20 ` [PATCH v2 2/3] mips: dts: ralink: mt7621: mux phy4 to gmac1 for GB-PC1 Arınç ÜNAL
2022-04-11 11:20 ` [PATCH v2 3/3] mips: dts: ralink: mt7621: remove defining gpio function for pin groups Arınç ÜNAL
2022-04-27 8:59 ` 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=20220427085914.GA8404@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).