From: Dragan Simic <dsimic@manjaro.org>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v3 2/2] arm64: dts: allwinner: a64: Add WiFi/BT header on SoPine
Date: Sun, 20 Apr 2025 19:17:48 +0200 [thread overview]
Message-ID: <e111f8b9f499a158af5fad1942951e0f@manjaro.org> (raw)
In-Reply-To: <CALeDE9Nyt7Di2_u-Vf=6OCAg-6wmbz75Cs_MCfZrk6upbD9nZw@mail.gmail.com>
Hello Peter,
On 2025-04-20 11:33, Peter Robinson wrote:
>> > This adds all the pin mappings on the WiFi/BT header on
>> > the SoPine baseboard/A64-LTS. They're disabled by default
>> > as the modules don't ship by default. This includes, where
>> > they haven't been already, UART1 for BT and mmc1 for WiFi.
>>
>> The patch subject should be improved a bit, to include
>> "Baseboard" as well. Having just "SoPine" is a bit too
>> vague, and it should actually be written as "SOPINE"
>> at all places in the prose.
>
> It literally has baseboard in the second line of the description.
True, but the patch subject should also contain "Baseboard",
because SOPINE is a system on module, and the SOPINE Baseboard
turns it into an SBC that actually has the add-on headers that
the patch addresses. I hope it makes sense.
next prev parent reply other threads:[~2025-04-20 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 16:00 [PATCH v3 0/2] Add support for WiFi/BT header on Pine64 A64 Peter Robinson
2025-04-19 16:00 ` [PATCH v3 1/2] arm64: dts: allwinner: a64: Add WiFi/BT header on Pine64 Peter Robinson
2025-04-19 18:25 ` Dragan Simic
2025-04-19 16:00 ` [PATCH v3 2/2] arm64: dts: allwinner: a64: Add WiFi/BT header on SoPine Peter Robinson
2025-04-19 18:25 ` Dragan Simic
[not found] ` <CALeDE9M_c7556sTdTC37Ce5vzLC2E8SV_P-J2CtFiUksdM_71Q@mail.gmail.com>
2025-04-19 19:57 ` Dragan Simic
2025-04-20 1:59 ` Chen-Yu Tsai
2025-04-20 2:13 ` Dragan Simic
2025-04-20 2:20 ` Chen-Yu Tsai
2025-04-20 9:33 ` Peter Robinson
2025-04-20 17:17 ` Dragan Simic [this message]
2025-04-20 17:42 ` Peter Robinson
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=e111f8b9f499a158af5fad1942951e0f@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=pbrobinson@gmail.com \
--cc=robh@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