From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: mpe@ellerman.id.au, Maxim Kiselev <bigunclemax@gmail.com>
Cc: devicetree@vger.kernel.org, andrew@lunn.ch,
vladimir.oltean@nxp.com, linux-kernel@vger.kernel.org,
fido_max@inbox.ru, robh+dt@kernel.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH v3] powerpc: dts: t1040rdb: fix ports names for Seville Ethernet switch
Date: Tue, 15 Feb 2022 16:26:32 +1100 [thread overview]
Message-ID: <164490279229.270256.13940315690425244509.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220121091447.3412907-1-bigunclemax@gmail.com>
On Fri, 21 Jan 2022 12:14:47 +0300, Maxim Kiselev wrote:
> On board rev A, the network interface labels for the switch ports
> written on the front panel are different than on rev B and later.
>
> This patch fixes network interface names for the switch ports according
> to labels that are written on the front panel of the board rev B.
> They start from ETH3 and end at ETH10.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: dts: t1040rdb: fix ports names for Seville Ethernet switch
https://git.kernel.org/powerpc/c/5ebb74749202a25da4b3cc2eb15470225a05527c
cheers
prev parent reply other threads:[~2022-02-15 5:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 10:43 [PATCH] powerpc: dts: t1040rdb: fix ports names for Seville Ethernet switch Maxim Kiselev
2021-12-30 13:00 ` Vladimir Oltean
2021-12-30 13:24 ` Maxim Kiselev
[not found] ` <20211231125247.ugne3h44pmpzliin@skbuf>
2022-01-10 7:40 ` Maxim Kiselev
2022-01-11 13:13 ` Vladimir Oltean
2022-01-11 15:22 ` [PATCH] powerpc: dts: add device tree for T1040RDB-REV-A Maxim Kiselev
2022-01-11 15:29 ` Vladimir Oltean
2022-01-11 17:37 ` [PATCH v2] powerpc: dts: t1040rdb: fix ports names for Seville Ethernet switch Maxim
2022-01-12 18:50 ` Vladimir Oltean
2022-01-20 6:29 ` Michael Ellerman
2022-01-21 9:14 ` [PATCH v3] " Maxim Kiselev
2022-02-15 5:26 ` Michael Ellerman [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=164490279229.270256.13940315690425244509.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=andrew@lunn.ch \
--cc=bigunclemax@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fido_max@inbox.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh+dt@kernel.org \
--cc=vladimir.oltean@nxp.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).