From: Ludwig Kormann <ludwig.kormann@in-circuit.de>
To: samuel@sholland.org, jernej.skrabec@gmail.com, wens@csie.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
andre.przywara@arm.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] arm: dts: sunxi: Add ICnova A20 ADB4006 board support
Date: Tue, 2 May 2023 10:06:20 +0200 [thread overview]
Message-ID: <10a2e893-18b6-d9c2-1db7-3d500cc0891c@in-circuit.de> (raw)
In-Reply-To: <20230420102409.1394618-1-ludwig.kormann@in-circuit.de>
Hello,
thanks for the reviews so far!
Is there anything I can do / need to do for my patch series for it to
get merged before -rc1?
The patch series was based on the "for-next" branch in jernej's tree,
but it seems that it was too late for the "dt-for-6.4" merge.
So I'm just trying to understand in general what the best way in this
situation would be:
- wait if someone else takes the patch series before -rc1
- wait for -rc1 and rebase, rework, send a new version of the patch
series (because of the planned restructuring of the ARM dts directory)
- wait for -rc3 (?) and rebase & rework the patch series for jernej's
tree for the "dt-for-6.5" branch
Thanks for your help.
kind regards
Ludwig Kormann
Am 20.04.23 um 12:24 schrieb Ludwig Kormann:
> Add board support for ICnova A20 SomPi compute module on
> ICnova ADB4006 development board.
>
> v3:
> - drop stray blank lines at end of files
> - separate patch for bindings
> - update licensing to "GPL-2.0 OR MIT"
> - fix typo: ICNova -> ICnova
>
> v2:
> - use short licensing header
> - remove deprecated elements from led nodes
> - disable csi power supply
> - add missing pins in usbphy node
> - split dts into SoM dtsi and carrier board dts
>
> v1 of this patch was sent to the uboot mailing list [1].
>
> [1] https://lists.denx.de/pipermail/u-boot/2023-April/514605.html
>
> Ludwig Kormann (2):
> dt-bindings: arm: sunxi: add ICnova A20 ADB4006 binding
> arm: dts: sunxi: Add ICnova A20 ADB4006 board
>
> .../devicetree/bindings/arm/sunxi.yaml | 6 +
> arch/arm/boot/dts/Makefile | 1 +
> .../boot/dts/sun7i-a20-icnova-a20-adb4006.dts | 137 ++++++++++++++++++
> arch/arm/boot/dts/sun7i-a20-icnova-a20.dtsi | 62 ++++++++
> 4 files changed, 206 insertions(+)
> create mode 100644 arch/arm/boot/dts/sun7i-a20-icnova-a20-adb4006.dts
> create mode 100644 arch/arm/boot/dts/sun7i-a20-icnova-a20.dtsi
>
next prev parent reply other threads:[~2023-05-02 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 10:24 [PATCH v3 0/2] arm: dts: sunxi: Add ICnova A20 ADB4006 board support Ludwig Kormann
2023-04-20 10:24 ` [PATCH v3 1/2] dt-bindings: arm: sunxi: add ICnova A20 ADB4006 binding Ludwig Kormann
2023-04-20 15:42 ` Krzysztof Kozlowski
2023-04-20 10:24 ` [PATCH v3 2/2] arm: dts: sunxi: Add ICnova A20 ADB4006 board Ludwig Kormann
2023-05-02 8:06 ` Ludwig Kormann [this message]
2023-05-02 9:13 ` [PATCH v3 0/2] arm: dts: sunxi: Add ICnova A20 ADB4006 board support Andre Przywara
2023-05-03 6:11 ` Krzysztof Kozlowski
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=10a2e893-18b6-d9c2-1db7-3d500cc0891c@in-circuit.de \
--to=ludwig.kormann@in-circuit.de \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox