Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "jurobystricky@hotmail.com" <jurobystricky@hotmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [morty][PATCH v2] gcc6.4 upgrade
Date: Sun, 11 Mar 2018 05:06:12 -0700	[thread overview]
Message-ID: <1520769972.10851.172.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQejU2YsEFWMydDJgbhtFP5r-e_45k7YqkUo3UdLRvbxVw@mail.gmail.com>

On Sun, 2018-03-11 at 01:56 +0100, Martin Jansa wrote:
> I've sent the pull requests for all 3 release branches.
> 
> I'll let some builders doing more tests over night, but it's very
> close to what was merged in master (and also to what is currently in
> morty-next) so it should be relatively safe.

Thanks for this. I've staged the patches in the various -next branches.
I ran pyro-next on the autobuilder to see where we stand and x86-64 is
showing the ICE I mentioned in valgrind so we'll likely need to pull
out that patch until we can figure out a way of fixing that. I'll queue
a fixup patch and retry and confirm that does fix the issue.

Cheers,

Richard




  reply	other threads:[~2018-03-11 12:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 23:49 [morty][PATCH v2] gcc6.4 upgrade Juro Bystricky
2018-03-09 23:49 ` [morty][PATCH v2] gcc6: Upgrade to 6.4.0 (latest stable series release) Juro Bystricky
2018-03-09 23:56 ` [morty][PATCH v2] gcc6.4 upgrade Bystricky, Juro
2018-03-10  0:36   ` akuster808
2018-03-10  7:46   ` Martin Jansa
2018-03-10 18:27     ` Richard Purdie
2018-03-10 21:04       ` Martin Jansa
2018-03-10 21:06         ` Martin Jansa
2018-03-10 21:34         ` Richard Purdie
2018-03-10 22:20           ` Andre McCurdy
2018-03-11  0:56           ` Martin Jansa
2018-03-11 12:06             ` Richard Purdie [this message]
2018-03-10  0:00 ` ✗ patchtest: failure for gcc6: Upgrade to 6.4.0 (latest stable series release) (rev3) Patchwork
2018-03-10  3:30   ` Andre McCurdy
2018-03-11  1:21     ` Martin Jansa
2018-03-10  1:42 ` [morty][PATCH v2] gcc6.4 upgrade Khem Raj
2018-03-10  2:25   ` Bystricky, Juro
2018-03-10  2:55     ` Andre McCurdy
2018-03-10  4:20       ` Khem Raj
2018-03-10 18:28         ` Bystricky, Juro

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=1520769972.10851.172.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jurobystricky@hotmail.com \
    --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