From: Sebastian Huber <sebastian.huber-L1vi/lXTdtsBbLBgBO8hYIQuADTiUCJX@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: fdtdump.c: Compile error with GCC 11
Date: Fri, 15 Jan 2021 06:22:19 +0100 [thread overview]
Message-ID: <8822ec89-7782-7608-cae5-e62770e28771@embedded-brains.de> (raw)
In-Reply-To: <20210106035431.GB3209-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>
On 06/01/2021 04:54, David Gibson wrote:
> Ah, I think I see what's going wrong here. I don't have easy access
> to gcc 11 to test with, so can you give this draft patch a test:
Sorry for the delay. This patch fixes the dtc build problem with GCC 11.
There were no other issues.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber-L1vi/lXTdtsBbLBgBO8hYIQuADTiUCJX@public.gmane.org
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2021-01-15 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 8:39 fdtdump.c: Compile error with GCC 11 Sebastian Huber
[not found] ` <db5d86de-fa1b-9d44-1188-edb81578bc00-L1vi/lXTdtsBbLBgBO8hYIQuADTiUCJX@public.gmane.org>
2021-01-06 3:54 ` David Gibson
[not found] ` <20210106035431.GB3209-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>
2021-01-15 5:22 ` Sebastian Huber [this message]
[not found] ` <8822ec89-7782-7608-cae5-e62770e28771-L1vi/lXTdtsBbLBgBO8hYIQuADTiUCJX@public.gmane.org>
2021-01-18 6:50 ` David Gibson
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=8822ec89-7782-7608-cae5-e62770e28771@embedded-brains.de \
--to=sebastian.huber-l1vi/lxtdtsbblbgbo8hyiquadtiucjx@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).