From: Michael Ellerman <mpe@ellerman•id.au>
To: "Pali Rohár" <pali@kernel•org>, "Rob Herring" <robh+dt@kernel•org>
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] powerpc: dts: Add DTS file for CZ.NIC Turris 1.x routers
Date: Fri, 24 Jun 2022 13:08:59 +1000 [thread overview]
Message-ID: <877d5669mc.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220511143712.22550-1-pali@kernel.org>
Pali Rohár <pali@kernel•org> writes:
> 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
>
> Signed-off-by: Pali Rohár <pali@kernel•org>
> ---
> arch/powerpc/boot/dts/turris1x.dts | 470 +++++++++++++++++++++++++++++
> 1 file changed, 470 insertions(+)
> create mode 100644 arch/powerpc/boot/dts/turris1x.dts
The headers say you Cc'ed this to the devicetree list, but I don't see
it in the devicetree patchwork:
https://patchwork.ozlabs.org/project/devicetree-bindings/list/?state=*&q=turris&archive=both
Which means it hasn't been run through Rob's CI scripts.
Maybe try a resend?
cheers
next prev parent reply other threads:[~2022-06-24 3:09 UTC|newest]
Thread overview: 9+ 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-24 9:23 ` Pali Rohár
2022-06-09 10:19 ` Pali Rohár
2022-06-22 12:35 ` Pali Rohár
2022-06-24 3:08 ` Michael Ellerman [this message]
2022-06-24 8:27 ` Pali Rohár
2022-06-24 9:30 ` Pali Rohár
2022-06-24 8:55 ` [PATCH v2] " Pali Rohár
2022-07-04 11:34 ` Michael Ellerman
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=877d5669mc.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=josef.schlehofer@nic$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=marek.behun@nic$(echo .)cz \
--cc=pali@kernel$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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