From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 5/5] WIP! arm64: dts: renesas: falcon: Add Ethernet-AVB1-5 support
Date: Fri, 22 Jan 2021 11:47:58 +0100 [thread overview]
Message-ID: <20210122104758.GB29150@kunai> (raw)
In-Reply-To: <CAMuHMdX1PoB-YNXvtr5dFMKu9OE8TdOB43fRfED_wVV6LhRU8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
> > .../boot/dts/renesas/r8a779a0-falcon-cpu.dtsi | 160 ++++++++++++++++++
>
> New file r8a779a0-falcon-ether.dtsi?
Makes sense.
>
> > + ins_mii {
>
> pins_mii
Now, how did that happen? Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-22 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:06 [PATCH v2 0/5] v3u: add support for RAVB Wolfram Sang
2021-01-21 10:06 ` [PATCH v2 1/5] dt-bindings: net: renesas,etheravb: Add r8a779a0 support Wolfram Sang
2021-01-23 3:31 ` Jakub Kicinski
2021-01-21 10:06 ` [PATCH v2 2/5] clk: renesas: r8a779a0: add clocks for RAVB Wolfram Sang
2021-01-22 10:16 ` Geert Uytterhoeven
2021-01-21 10:06 ` [PATCH v2 3/5] arm64: dts: renesas: r8a779a0: Add Ethernet-AVB support Wolfram Sang
2021-01-22 10:20 ` Geert Uytterhoeven
2021-01-21 10:06 ` [PATCH v2 4/5] arm64: dts: renesas: falcon: Add Ethernet-AVB0 support Wolfram Sang
2021-01-22 10:23 ` Geert Uytterhoeven
2021-01-21 10:06 ` [PATCH v2 5/5] WIP! arm64: dts: renesas: falcon: Add Ethernet-AVB1-5 support Wolfram Sang
2021-01-22 10:26 ` Geert Uytterhoeven
2021-01-22 10:47 ` Wolfram Sang [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=20210122104758.GB29150@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
/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.