From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] socketcand: resolve GCC5 related issue
Date: Wed, 22 Jul 2015 22:30:51 +0200 [thread overview]
Message-ID: <20150722223051.3ebbf80a@free-electrons.com> (raw)
In-Reply-To: <1437591146-12969-1-git-send-email-yegorslists@googlemail.com>
Dear Yegor Yefremov,
On Wed, 22 Jul 2015 20:52:26 +0200, Yegor Yefremov wrote:
> This patch removes inline keyword from header and source
> files.
>
> Fixes following autobuild failure:
> http://autobuild.buildroot.net/results/8ea/8eac9832554dbd1f2e14cf54e5c99e6bf4dfc2cc/
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> .../socketcand/0001-Remove-inline-keyword.patch | 90 ++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
> create mode 100644 package/socketcand/0001-Remove-inline-keyword.patch
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-22 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 18:52 [Buildroot] [PATCH] socketcand: resolve GCC5 related issue Yegor Yefremov
2015-07-22 20:30 ` 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=20150722223051.3ebbf80a@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