From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Rob Herring <robh+dt@kernel.org>, Pali Rohár <pali@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: devicetree@vger.kernel.org,
Josef Schlehofer <josef.schlehofer@nic.cz>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Marek Behun <marek.behun@nic.cz>
Subject: Re: [PATCH v2] powerpc: dts: Add DTS file for CZ.NIC Turris 1.x routers
Date: Mon, 04 Jul 2022 21:34:09 +1000 [thread overview]
Message-ID: <165693444903.9954.14449281887878429329.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220624085550.20570-1-pali@kernel.org>
On Fri, 24 Jun 2022 10:55:50 +0200, Pali Rohár wrote:
> CZ.NIC Turris 1.0 and 1.1 are open source routers, they have dual-core
> PowerPC Freescale P2020 CPU and are based on Freescale P2020RDB-PC-A board.
> Hardware design is fully open source, all firmware and hardware design
> files are available at Turris project website:
>
> https://docs.turris.cz/hw/turris-1x/turris-1x/
> https://project.turris.cz/en/hardware.html
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: dts: Add DTS file for CZ.NIC Turris 1.x routers
https://git.kernel.org/powerpc/c/54c15ec3b738c6086f2be001dae962ec412640e5
cheers
prev parent reply other threads:[~2022-07-04 11:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 14:37 [PATCH] powerpc: dts: Add DTS file for CZ.NIC Turris 1.x routers Pali Rohár
2022-05-11 14:37 ` Pali Rohár
2022-05-24 9:23 ` Pali Rohár
2022-05-24 9:23 ` Pali Rohár
2022-06-09 10:19 ` Pali Rohár
2022-06-09 10:19 ` Pali Rohár
2022-06-22 12:35 ` Pali Rohár
2022-06-22 12:35 ` Pali Rohár
2022-06-24 3:08 ` Michael Ellerman
2022-06-24 3:08 ` Michael Ellerman
2022-06-24 8:27 ` Pali Rohár
2022-06-24 8:27 ` Pali Rohár
2022-06-24 9:30 ` Pali Rohár
2022-06-24 9:30 ` Pali Rohár
2022-06-24 8:55 ` [PATCH v2] " Pali Rohár
2022-06-24 8:55 ` Pali Rohár
2022-07-04 11:34 ` 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=165693444903.9954.14449281887878429329.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=devicetree@vger.kernel.org \
--cc=josef.schlehofer@nic.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=marek.behun@nic.cz \
--cc=mpe@ellerman.id.au \
--cc=pali@kernel.org \
--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.