Re: [PATCH v2 0/4] Add BigTreeTech CB1 SoM & Boards

From: Marijn Suijten
Date: Fri Aug 04 2023 - 09:58:48 EST


On 2023-08-04 11:00:28, Martin Botka wrote:
> Hello,
> This series adds a vendor prefix for BigTreeTech and adds BigTreeTech CB1,
> Manta board and BigTreeTech Pi.
>
> CB1 is just an SoM thats based on AllWinner H616.
> BigTreeTech Manta boards are expander boards for CB1 and BigTreeTech Pi
> is an CB1 in Rpi style with few additional things like IR receiver and fan port
> on GPIO.
>
> This work started before I was hired by BigTreeTech and thus majority of the
> patches are from SoMainline email and few are from my work email.
>
> This series depends on commit https://lkml.org/lkml/2023/8/2/801
> "dt-bindings: mfd: x-powers,axp152: make interrupt optional for more chips".
>
> Cheers,
> Martin
>
> Martin Botka (4):
> dt-bindings: vendor-prefixes: Add BigTreeTech
> dt-bindings: arm: sunxi: Add BigTreeTech boards
> arm64: dts: allwinner: h616: Add BigTreeTech CB1 SoM & boards support
> arm64: dts: allwinner: h616: Add BigTreeTech Pi support
>
> .../devicetree/bindings/arm/sunxi.yaml | 11 ++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> arch/arm64/boot/dts/allwinner/Makefile | 2 +
> .../sun50i-h616-bigtreetech-cb1-manta.dts | 35 +++++
> .../sun50i-h616-bigtreetech-cb1.dtsi | 142 ++++++++++++++++++
> .../allwinner/sun50i-h616-bigtreetech-pi.dts | 68 +++++++++
> 6 files changed, 260 insertions(+)
> create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h616-bigtreetech-cb1-manta.dts
> create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h616-bigtreetech-cb1.dtsi
> create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h616-bigtreetech-pi.dts
>
> --
> 2.41.0
>

The In-Reply-To header in this v2 series is also not pointing to the
cover letter, making all patches detached in my (and presumably others')
mailbox.

Here's what seems to be going on. Something prepends an extra
identifier (before the +) to the Message-ID of the cover letter (and all
your other mails):

Message-ID: <DC7CD91802A925BE+20230804090102.273029-1-martin@xxxxxxxxxx>

This is however not reflected in the patches of this series, which still
"reply to" the unmodified Message-ID:

In-Reply-To: <20230804090102.273029-1-martin@xxxxxxxxxx>

As such, they don't seem to reply to an existing mail in my inbox, and
are hence not parented.

I doubt this is a "feature" that modern mail clients are supposed to
understand, or at least neomutt doesn't (and IIRC ThunderBird didn't
either). Can you figure out, possibly with your SMTP server (provider),
how to prevent this before sending another series? It wasn't a problem
when mails originated from SoMainline.org.

- Marijn