From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] edid: Fix gcc 7.1 warning
Date: Wed, 24 May 2017 06:35:12 +0200 [thread overview]
Message-ID: <3615818.mLb3oUA55I@jernej-laptop> (raw)
In-Reply-To: <20170524010016.GS23727@bill-the-cat>
Hi,
Dne sreda, 24. maj 2017 ob 03:00:16 CEST je Tom Rini napisal(a):
> On Tue, May 23, 2017 at 11:05:30PM +0200, Jernej Skrabec wrote:
> > This commit fixes the warning produced by gcc 7.1.
> >
> > Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
>
> And I'm curious, where is your gcc-7.1 toolchain from, self built or
> something else? Thanks!
It's from Arch Linux repository.
I'm sorry to say that there seems to be something wrong with either gcc 7.1 or
bootp code. With OrangePi 2 board, bootp crashes and resets the board
(ethernet cable is not connected). I didn't have time to investigate it
further.
Best regards,
Jernej
next prev parent reply other threads:[~2017-05-24 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 21:05 [U-Boot] [PATCH] edid: Fix gcc 7.1 warning Jernej Skrabec
2017-05-24 1:00 ` Tom Rini
2017-05-24 4:35 ` Jernej Škrabec [this message]
2017-05-24 6:56 ` Peter Robinson
2017-06-01 3:10 ` Simon Glass
2017-06-02 7:57 ` Anatolij Gustschin
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=3615818.mLb3oUA55I@jernej-laptop \
--to=jernej.skrabec@siol.net \
--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