From: Paul Barker <paul.barker@sancloud.com>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config
Date: Thu, 17 Jun 2021 11:31:56 +0100 [thread overview]
Message-ID: <20210617113157.06c6f026.paul.barker@sancloud.com> (raw)
In-Reply-To: <CALeDE9N34_xTpLsDzU_2Tyf_0nfw0oKTX0WO30X4MdVoUdPJyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Thu, 17 Jun 2021 11:05:46 +0100
Peter Robinson <pbrobinson@gmail.com> wrote:
> On Thu, Jun 17, 2021 at 10:03 AM Paul Barker
> <paul.barker@sancloud.com> wrote:
> >
> > Configuration which is shared between the BeagleBone Black and
> > derivative boards like the Sancloud BeagleBone Enhanced (BBE) is
> > moved to a common dtsi file to prevent duplication.
>
> Are these being sent upstream to the linux kernel?
The upstream kernel already has am335x-boneblack-common.dtsi and
am335x-sancloud-bbe.dts files, since 2016 and 2018 respectively. As
these files fell out of sync over 4 years ago I've assumed there is no
need to keep them in sync. We could try to resync things but that would
lead to an unnecessary risk of breakage, I don't have every BeagleBone
Black derivative board on hand to fully test such a resync.
--
Paul Barker
Principal Software Engineer
SanCloud Ltd
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-06-17 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:02 [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Paul Barker
2021-06-17 9:02 ` [PATCH 2/4] arm: dts: am335x-sancloud-bbe: New dtb to support ethernet Paul Barker
2021-06-17 9:02 ` [PATCH 3/4] configs: am335x_evm: Support GbE PHYs Paul Barker
2021-06-17 9:02 ` [PATCH 4/4] configs: am335x_evm: Fix BeagleBone Green DTB selection Paul Barker
2021-06-17 10:05 ` [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Peter Robinson
2021-06-17 10:31 ` Paul Barker [this message]
2021-06-17 10:35 ` Peter Robinson
2021-06-17 10:49 ` Paul Barker
2021-06-17 12:27 ` Tom Rini
2021-07-12 16:23 ` Paul Barker
2021-07-13 5:58 ` Lokesh Vutla
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=20210617113157.06c6f026.paul.barker@sancloud.com \
--to=paul.barker@sancloud.com \
--cc=pbrobinson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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