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:28:59 +0000 [thread overview]
Message-ID: <1520170139.3436.68.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQeV1f7yUt3w5t7iXrYf5OyMjbxr-C_dqKGqG+jDt4gFcA@mail.gmail.com>
On Sun, 2018-03-04 at 12:38 +0100, Martin Jansa wrote:
> Is this backport of https://patches.openembedded.org/patch/144961/ ?
>
> If yes, why does it have different author?
I suspect this was done independently and it wasn't realised that there
was a patch that could be backported. We'll wait for Juro to comment.
I posted it as I really wanted to get it reviewed, it passed the test
builds and I'm keen to get some of these issues resolved before travel
starts complicating things for me.
Cheers,
Richard
prev parent reply other threads:[~2018-03-04 13:29 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
2018-03-04 13:25 ` Richard Purdie
2018-03-04 13:33 ` Martin Jansa
2018-03-04 13:28 ` Richard Purdie [this message]
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=1520170139.3436.68.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