From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Fix for gcc bug 61144
Date: Sat, 11 Oct 2014 08:05:33 +0100 [thread overview]
Message-ID: <1413011133.7562.5.camel@ted> (raw)
In-Reply-To: <54381C20.2060602@linux.intel.com>
On Fri, 2014-10-10 at 10:49 -0700, Saul Wold wrote:
> On 10/10/2014 09:40 AM, Peter Urbanec wrote:
> > See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61144 for details.
> >
> > This patch is taken from the gcc repository and should be obsoleted by a
> > gcc release after 4.9.1
> >
> > The problem is severe enough (at least from my point of view) to need
> > this patch until the next gcc release is available.
> >
> >
> >
> >
>
> Hi Peter
>
> Thank you for the patches.
>
> Both the patch and the 0056-top-level-reorder_gcc-bug-61144.patch patch
> file need to have Signed-off-by tags and the gcc patch itself needs an
> Upstream-Status: Backport tag so we know it was a backport.
>
> Please review the
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>
> I also note the second patch you sent does not have a Signed-off-by in
> the commit message or the .patch files (which also needs an
> Upstream-Status tag).
>
> Can you please send a V2 updates commit for both of these.
Just to be clear, because of the important nature of the gcc fix and our
looming release deadlines, Saul has sent out a version of it in this
case. We don't normally do that.
Cheers,
Richard
next prev parent reply other threads:[~2014-10-11 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:40 [PATCH] Fix for gcc bug 61144 Peter Urbanec
2014-10-10 17:49 ` Saul Wold
2014-10-11 7:05 ` Richard Purdie [this message]
2014-10-13 3:00 ` Peter Urbanec
-- strict thread matches above, loose matches on Subject: below --
2014-10-09 13:12 Peter Urbanec
2014-10-10 10:43 ` Martin Jansa
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=1413011133.7562.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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.