From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] Dockerfile: Switch to gcc 9.2.0
Date: Mon, 6 Apr 2020 08:36:10 -0400 [thread overview]
Message-ID: <20200406123610.GM27133@bill-the-cat> (raw)
In-Reply-To: <1586176380-29706-1-git-send-email-bmeng.cn@gmail.com>
On Mon, Apr 06, 2020 at 05:33:00AM -0700, Bin Meng wrote:
> Use gcc 9.2.0 to do the build testing.
>
> Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Oh nice. Do we luck out and have no new warnings to fix? 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/20200406/2b2746fb/attachment.sig>
next prev parent reply other threads:[~2020-04-06 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 12:33 [PATCH] Dockerfile: Switch to gcc 9.2.0 Bin Meng
2020-04-06 12:36 ` Tom Rini [this message]
2020-04-06 12:50 ` Bin Meng
2020-04-10 22:24 ` 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=20200406123610.GM27133@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