From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH v3 3/3] RFC: CI: Skip building dtc for world builds
Date: Mon, 14 Oct 2024 16:43:06 -0600 [thread overview]
Message-ID: <20241014224306.GG53053@bill-the-cat> (raw)
In-Reply-To: <CAFLszTjFeT+OKLrUT1Ck_D15nqxoJcq18LMmWFbJAwQocEvm4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Mon, Oct 14, 2024 at 01:13:26PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Thu, 10 Oct 2024 at 13:01, Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Oct 10, 2024 at 12:50:11PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Thu, 15 Aug 2024 at 13:58, Simon Glass <sjg@chromium.org> wrote:
> > > >
> > > > This is quite a significant waste of time in the world builds as dtc is
> > > > built separately for each board. Skip this to speed up the builds.
> > > >
> > > > Unfortunately the newer dtc produces a lot of warnings, which causes CI
> > > > to fail. I am not sure what we can do about this.
> > >
> > > What do you think about this one?
> > >
> > > We could install an older dtc in the container, perhaps?
> >
> > Is backporting applying whatever dtc flags we need to ignore problems
> > that Linux isn't enforcing so difficult? That would then tell us just
> > how much work it is / isn't to deal with the rest of the dts files (or
> > poke maintainers to switch to OF_UPSTREAM where the issues are likely
> > fixed).
>
> That could work. Shall I give it a try and then we apply this patch if
> I figure it out?
Sure, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-14 22:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 19:57 [PATCH v3 0/3] This series adds a few patches to make it easy to use the system dtc in Simon Glass
2024-08-15 19:57 ` [PATCH v3 1/3] buildman: Support building within a Python venv Simon Glass
2024-09-06 0:53 ` Simon Glass
2024-08-15 19:57 ` [PATCH v3 2/3] buildman: Allow skipping the dtc build Simon Glass
2024-08-16 17:22 ` Tom Rini
2024-08-16 23:53 ` Simon Glass
2024-08-22 3:00 ` Simon Glass
2024-08-22 14:10 ` Tom Rini
2024-08-22 14:15 ` Simon Glass
2024-09-01 20:09 ` Simon Glass
2024-09-02 15:39 ` Tom Rini
2024-09-10 18:41 ` Simon Glass
2024-09-10 18:42 ` Tom Rini
2024-09-10 18:45 ` Simon Glass
2024-09-10 18:52 ` Tom Rini
2024-09-10 20:14 ` Simon Glass
2024-09-10 22:07 ` Tom Rini
2024-09-12 1:01 ` Simon Glass
2024-09-12 17:44 ` Tom Rini
2024-09-19 14:13 ` Simon Glass
2024-09-26 22:07 ` Simon Glass
2024-08-15 19:57 ` [PATCH v3 3/3] RFC: CI: Skip building dtc for world builds Simon Glass
2024-10-10 18:50 ` Simon Glass
2024-10-10 19:01 ` Tom Rini
2024-10-14 19:13 ` Simon Glass
2024-10-14 22:43 ` Tom Rini [this message]
2024-09-06 22:37 ` (subset) [PATCH v3 0/3] This series adds a few patches to make it easy to use the system dtc in Tom Rini
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=20241014224306.GG53053@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrejs.cainikovs@toradex.com \
--cc=jiaxun.yang@flygoat.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--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