From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] libfdt: Fix signedness comparison warnings
Date: Fri, 16 Oct 2020 10:57:19 -0400 [thread overview]
Message-ID: <20201016145719.GV14816@bill-the-cat> (raw)
In-Reply-To: <20201016144250.29106-1-andre.przywara@arm.com>
On Fri, Oct 16, 2020 at 03:42:50PM +0100, Andre Przywara wrote:
> This is a combination of upstream libfdt commits to fix warnings about
> comparing signed and unsigned integers:
> ==========
> scripts/dtc/libfdt/fdt.c: In function ?fdt_offset_ptr?:
> scripts/dtc/libfdt/fdt.c:137:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> if ((absoffset < offset)
> ...
> ==========
>
> For a detailed description of the fixes, see the dtc repo:
> https://git.kernel.org/pub/scm/utils/dtc/dtc.git/log/?id=73e0f143b73d808
>
> For this patch the commits between 73e0f143b73d8088 and ca19c3db2bf62000
> have been combined and adjusted for the slight differences in U-Boot's
> libfdt code base.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
So, the scripts that the Linux kernel uses to re-sync with dtc also work
for U-Boot. Has the kernel re-synced yet? If so, can we just re-sync
with that same commit again? That's typically how we do this. 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/20201016/11f4c6f6/attachment.sig>
next prev parent reply other threads:[~2020-10-16 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 14:42 [PATCH] libfdt: Fix signedness comparison warnings Andre Przywara
2020-10-16 14:57 ` Tom Rini [this message]
2020-10-16 15:22 ` Tom Rini
2020-11-11 14:52 ` 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=20201016145719.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