public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Re-syncing U-Boot DTS with the kernel again
Date: Wed, 11 Nov 2020 09:50:16 -0500	[thread overview]
Message-ID: <20201111145016.GE5340@bill-the-cat> (raw)
In-Reply-To: <dbc95254-559a-b36a-54b2-3f75425fcbc2@microchip.com>

On Wed, Nov 11, 2020 at 11:07:11AM +0000, Eugen.Hristev at microchip.com wrote:
> On 23.10.2020 19:05, Tom Rini wrote:
> 
> Hello Tom,
> 
> The at91/atmel related devicetrees should be fixed now in 2021.01-rc2.
> 
> Do you plan to update the DTC for 2021.01 final or for a future release ?

I think the safest plan is to take the patch that fixes gcc-10 warnings
now (and only has minor actual code changes) and resync dtc again post
v2021.01.  I'm quite happy to see the dts resyncs that have happened,
but there's a few more that need to happen before we can move to a newer
version, without disabling warnings at least.  And I think I need to dig
out / post the sandbox ones.

-- 
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/20201111/6035d175/attachment.sig>

      reply	other threads:[~2020-11-11 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 16:05 Re-syncing U-Boot DTS with the kernel again Tom Rini
2020-11-06  8:17 ` Patrice CHOTARD
2020-11-11 11:07 ` Eugen.Hristev at microchip.com
2020-11-11 14:50   ` Tom Rini [this message]

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=20201111145016.GE5340@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