From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Re-syncing U-Boot DTS with the kernel again
Date: Fri, 23 Oct 2020 12:05:39 -0400 [thread overview]
Message-ID: <20201023160539.GV14816@bill-the-cat> (raw)
Hey all,
As part of moving us up again to a recent dtc snapshot (and get in sync
with the Linux kernel and get some useful bugfixes), a bunch of new dtc
warnings are showing up in our tree. These have all been fixed in
upstream Linux I do believe, so it's a matter of doing a full or partial
resync again with Linux to resolve these. The warnings are about
spi_bus_bridge or spi_bus_reg. The full build logs can be seen over at:
https://gitlab.denx.de/u-boot/u-boot/-/jobs/168091
https://gitlab.denx.de/u-boot/u-boot/-/jobs/168092
https://gitlab.denx.de/u-boot/u-boot/-/jobs/168093
https://gitlab.denx.de/u-boot/u-boot/-/jobs/168094
I've put a WIP/resync-dtc-v1.6.0-31-gcbca977ea121-v4 bring up and I'll
try and not rebase that yet again now that I'm posting it, but it's not
intended to merge as-is. I really don't want to go back to the point
where we have tons of warnings being generated over device trees again,
so we need to have a plan to fix these. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201023/9745e3e1/attachment.sig>
next reply other threads:[~2020-10-23 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 16:05 Tom Rini [this message]
2020-11-06 8:17 ` Re-syncing U-Boot DTS with the kernel again Patrice CHOTARD
2020-11-11 11:07 ` Eugen.Hristev at microchip.com
2020-11-11 14:50 ` 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=20201023160539.GV14816@bill-the-cat \
--to=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