All of lore.kernel.org
 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: Sat, 10 Mar 2018 13:34:17 -0800	[thread overview]
Message-ID: <1520717657.10851.169.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQfpguoc3aumUZbo-3V1n2wyGyHdzwyJ2EeXFemFUOd-7Q@mail.gmail.com>

On Sat, 2018-03-10 at 22:04 +0100, Martin Jansa wrote:
> Feel free to ignore my feedback.
> 
> I didn't mean it as strong objection to get this merged as-is.
> 
> It was rather an advice for next time or in case another version is
> sent (e.g. with that missing patch from Khem) and Juro decides to
> rework it in order to save himself some time later when preparing the
> changes for pyro and rocko (as he said in the e-mail that he plans to
> prepare). It shouldn't be too difficult to rework anyway, because
> Andre already has the cherry-picks for morty and Juro can do just
> rebase of his change on top of that to get those new patches in
> separate commit.

Juro's mail reply was a bit messed up with formatting but that missing
arm patch appeared to cause an internal compiler error when compiling
valgrind for x86-64 and I suspect that is why its missing. If we do
want to consider that one I'd probably make it a separate issue.

I can't really merge anything due to our backports policy until we have
at least the pyro patches sorted. I'm still torn on which way to go but
if someone can pull together a good set of patches for the various
branches I would take it. I'm also pretty sure Juro will be fine if
someone wants to break that patch up.

Cheers,

Richard




  parent reply	other threads:[~2018-03-10 21:34 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 [this message]
2018-03-10 22:20           ` Andre McCurdy
2018-03-11  0:56           ` Martin Jansa
2018-03-11 12:06             ` Richard Purdie
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=1520717657.10851.169.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.