From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v1 2/3] MIPS: ath79: ar9331: Add OpeneEmbed SOM9331 Board
Date: Thu, 27 May 2021 13:43:34 +0200 [thread overview]
Message-ID: <20210527114334.GE9210@alpha.franken.de> (raw)
In-Reply-To: <20210514051743.15248-2-o.rempel@pengutronix.de>
On Fri, May 14, 2021 at 07:17:42AM +0200, Oleksij Rempel wrote:
> Add SOM9331 based Board. It has 3 LAN ports, usb to uart controller and
> USB type A port.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> arch/mips/boot/dts/qca/Makefile | 1 +
> .../qca/ar9331_openembed_som9331_board.dts | 110 ++++++++++++++++++
> 2 files changed, 111 insertions(+)
> create mode 100644 arch/mips/boot/dts/qca/ar9331_openembed_som9331_board.dts
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 ]
next prev parent reply other threads:[~2021-05-27 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 5:17 [PATCH v1 1/3] dt-bindings: vendor-prefixes: Add an entry for OpenEmbed Oleksij Rempel
2021-05-14 5:17 ` [PATCH v1 2/3] MIPS: ath79: ar9331: Add OpeneEmbed SOM9331 Board Oleksij Rempel
2021-05-27 11:43 ` Thomas Bogendoerfer [this message]
2021-05-14 5:17 ` [PATCH v1 3/3] MIPS: ath79: ar9331: add pause property for the MAC <> switch link Oleksij Rempel
2021-05-27 11:43 ` Thomas Bogendoerfer
2021-05-18 1:21 ` [PATCH v1 1/3] dt-bindings: vendor-prefixes: Add an entry for OpenEmbed Rob Herring
2021-05-27 11:43 ` Thomas Bogendoerfer
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=20210527114334.GE9210@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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.