From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] webkitgtk: add upstream patch for failed gcc6 builds
Date: Tue, 11 Oct 2016 12:16:25 +0200 [thread overview]
Message-ID: <20161011121625.0b595c92@free-electrons.com> (raw)
In-Reply-To: <1476133392-11842-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Mon, 10 Oct 2016 18:03:12 -0300, Gustavo Zacarias wrote:
> diff --git a/package/webkitgtk/0001-fix-gcc6-builds.patch b/package/webkitgtk/0001-fix-gcc6-builds.patch
> new file mode 100644
> index 0000000..83e038a
> --- /dev/null
> +++ b/package/webkitgtk/0001-fix-gcc6-builds.patch
> @@ -0,0 +1,40 @@
> +Upstream, from: https://trac.webkit.org/changeset/205672
> +
> +Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
This description is a bit short, so I copy/pasted the description of
the upstream patch here.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-11 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 21:03 [Buildroot] [PATCH] webkitgtk: add upstream patch for failed gcc6 builds Gustavo Zacarias
2016-10-11 10:16 ` Thomas Petazzoni [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=20161011121625.0b595c92@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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