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: [ANN] U-Boot v2021.01-rc2 released
Date: Tue, 10 Nov 2020 07:16:01 -0500	[thread overview]
Message-ID: <20201110121601.GX5340@bill-the-cat> (raw)
In-Reply-To: <d4b1f314-e60a-c712-3171-49fdc5ad85e7@gmx.de>

On Tue, Nov 10, 2020 at 01:00:06PM +0100, Heinrich Schuchardt wrote:
> On 11/10/20 11:41 AM, Andy Shevchenko wrote:
> > On Tue, Nov 10, 2020 at 12:40 PM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> > > 
> > > On Tue, Nov 10, 2020 at 12:22 AM Tom Rini <trini@konsulko.com> wrote:
> > > > 
> > > > Hey all,
> > > > 
> > > > It's regular release day and I'm back on schedule, so here's -rc2.
> > > > 
> > > > There's a few small'ish things outstanding in my queue, and a queue of
> > > > things building up for -next already.  I'm going to try and make sure
> > > > what I pull in, even when a clean-up, is as close as can be to the
> > > > obviously correct side of things.  Yes, this should always be the case,
> > > > I'm just going to try and hold myself to expectations a bit harder.
> > > > 
> > > > In terms of a changelog,
> > > > git log --merges v2021.01-rc1..v2021.01-rc2
> > > > contains what I've pulled but as always, better PR messages and tags
> > > > will provide better results here.
> > > > 
> > > > I do have my reminders setup for doing -rc releases every other Monday
> > > > from here on out and final release on January 11th, 2021.  Thanks all!
> > > 
> > > fdt.c is full of
> > 
> > Correction: all of fdt*.c are full of this kind of compiler warnings
> > 
> > > scripts/dtc/libfdt/fdt.c: In function ?fdt_offset_ptr?:
> > > scripts/dtc/libfdt/fdt.c:137:18: warning: comparison of integer
> > > expressions of different signedness: ?unsigned int? and ?int?
> > > [-Wsign-compare]
> > >   137 |   if ((absoffset < offset)
> > >       |                  ^
> > > 
> > > Is it known? Is a fix available?

With what compiler version?

> Yes adjust the integer types. Pease, send patches upstream.

This is probably what Andre posted patches for a few weeks ago, and in
turn got me to try and work with upstream dtc to come up with a way to
deal with the unaligned access safe default load functions that in turn
ruin boot times.

-- 
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/20201110/cec23cce/attachment.sig>

  reply	other threads:[~2020-11-10 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 22:21 [ANN] U-Boot v2021.01-rc2 released Tom Rini
2020-11-10 10:40 ` Andy Shevchenko
2020-11-10 10:41   ` Andy Shevchenko
2020-11-10 12:00     ` Heinrich Schuchardt
2020-11-10 12:16       ` Tom Rini [this message]
2020-11-10 12:18         ` Heinrich Schuchardt
2020-11-10 12:35           ` Tom Rini
2020-11-10 14:54             ` Andy Shevchenko

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=20201110121601.GX5340@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