From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/urg: fix build with gcc-6
Date: Mon, 12 Sep 2016 22:41:43 +0200 [thread overview]
Message-ID: <20160912224143.06cec550@free-electrons.com> (raw)
In-Reply-To: <20160912192324.23682-2-s.martin49@gmail.com>
Hello,
On Mon, 12 Sep 2016 21:23:23 +0200, Samuel Martin wrote:
> Add patch fixing/adding explicit cast on negative value in char[], which
> is required with gcc-6 (see "Narrowing conversions" paragraph in [1])
>
> Fixes:
> http://autobuild.buildroot.net/results/d0c/d0cd11163753db69a14c02e941dbda40e5f98bba/
>
> [1] https://gcc.gnu.org/gcc-6/porting_to.html
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
I don't see this patch in patchwork. Did you remove it from patchwork
somehow ? Or was patchwork confused by something in your patch ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-12 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 19:23 [Buildroot] [PATCH 1/3] package/urg: fix build Samuel Martin
2016-09-12 19:23 ` [Buildroot] [PATCH 2/3] package/urg: fix build with gcc-6 Samuel Martin
2016-09-12 20:41 ` Thomas Petazzoni [this message]
2016-09-13 4:19 ` Samuel Martin
2016-09-13 6:38 ` Arnout Vandecappelle
2016-10-15 10:24 ` Thomas Petazzoni
2016-09-12 19:23 ` [Buildroot] [PATCH 3/3] package/nginx-naxsi: add missing pcre dependency Samuel Martin
2016-09-12 20:39 ` Thomas Petazzoni
2016-09-13 6:40 ` Arnout Vandecappelle
2016-09-13 7:57 ` Samuel Martin
2016-09-13 17:30 ` Arnout Vandecappelle
2016-09-13 17:52 ` Samuel Martin
2016-09-14 11:45 ` Thomas Petazzoni
2016-09-12 20:41 ` [Buildroot] [PATCH 1/3] package/urg: fix build Thomas Petazzoni
2016-09-14 9:47 ` Thomas Petazzoni
2016-09-15 4:37 ` Samuel Martin
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=20160912224143.06cec550@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 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.