From: "Heiko Stübner" <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-rockchip@lists.infradead.org,
Thomas McKahan <tmckahan@singleboardsolutions.com>
Cc: Thomas McKahan <tmckahan@singleboardsolutions.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add Support for the FriendlyElec NanoPC T6
Date: Wed, 09 Aug 2023 12:43:50 +0200 [thread overview]
Message-ID: <12777866.O9o76ZdvQC@diego> (raw)
In-Reply-To: <20230809054213.27447-1-tmckahan@singleboardsolutions.com>
Hi Thomas,
Am Mittwoch, 9. August 2023, 07:42:08 CEST schrieb Thomas McKahan:
> Hello,
>
> This adds support for the RK3588-based NanoPC T6 single board computer.
> Note this series is dependent on the PCIe 3 support [0] being
> upstreamed. The NanoPC T6 uses PCIe3x4 like the Rock 5B and EVB1.
>
> [0] https://lore.kernel.org/all/20230717173512.65169-1-sebastian.reichel@collabora.com/
>
> v2:
> - remove unnecessary "okay" status from sound
> - add '-regulator' suffix on 2 regulators that were missing them
> - use generic node name for rtc
> - remove extra lines
> - fix alignment in I2S entry
>
> v1: https://lore.kernel.org/all/20230802051441.3106-1-tmckahan@singleboardsolutions.com/
>
> Thomas McKahan (2):
> dt-bindings: arm: rockchip: Add NanoPC T6
> arm64: dts: rockchip: Add NanoPC T6
somehow the actual patches are missing from this submission?
I also checked the linux-rockchip archive, and they're missing
there too.
I guess you'll need to resend or check where they took the wrong exit.
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-09 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 5:42 [PATCH v2 0/2] Add Support for the FriendlyElec NanoPC T6 Thomas McKahan
2023-08-09 10:43 ` Heiko Stübner [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=12777866.O9o76ZdvQC@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=tmckahan@singleboardsolutions.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).