From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][pyro] gcc6: Upgrade to 6.4.0 (latest stable series release)
Date: Sun, 04 Mar 2018 13:48:41 +0000 [thread overview]
Message-ID: <1520171321.3436.71.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQcjfrZMv=oSByNCeFK-=yXFy=3NReYGx9q4jX+MDBmwgg@mail.gmail.com>
On Sun, 2018-03-04 at 14:40 +0100, Martin Jansa wrote:
> I'm sorry, for some reason this thread in Gmail starts with the morty
> review you've sent, but when I look in my favorite mutt, I see that
> my replies were linked with pyro review where you're right the files
> aren't included.
>
> Still I would like to see what's the diff between gcc-6.4 in morty
> and pyro and gcc-6.4 which was in master (and there is still gcc-6.3
> in rocko which should imho be upgraded first to preserve continuity).
Right, I was looking at pyro-next since that was the patch you'd
replied to!
I'm not sure why those files are there, they likely shouldn't be. Juro?
I also agree on upgrading rocko gcc6, the trouble there is testing, its
not the default compiler and our testing doesn't cover it :/. Anyone
willing to sort out a patch?
Cheers,
Richard
next prev parent reply other threads:[~2018-03-04 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 11:23 [PATCH][pyro] gcc6: Upgrade to 6.4.0 (latest stable series release) Richard Purdie
2018-03-04 11:35 ` ✗ patchtest: failure for gcc6: Upgrade to 6.4.0 (latest stable series release) (rev2) Patchwork
2018-03-04 11:38 ` [PATCH][pyro] gcc6: Upgrade to 6.4.0 (latest stable series release) Martin Jansa
2018-03-04 12:00 ` Martin Jansa
2018-03-04 12:08 ` Martin Jansa
2018-03-04 13:26 ` Richard Purdie
2018-03-04 13:35 ` Martin Jansa
2018-03-04 13:40 ` Martin Jansa
2018-03-04 13:48 ` Richard Purdie [this message]
2018-03-04 13:25 ` Richard Purdie
2018-03-04 13:33 ` Martin Jansa
2018-03-04 13:28 ` Richard Purdie
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=1520171321.3436.71.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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