From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kmscube: bump version to fix build failures
Date: Tue, 14 Mar 2017 23:42:03 +0100 [thread overview]
Message-ID: <20170314234203.5e3d0194@free-electrons.com> (raw)
In-Reply-To: <1489422381-6163-1-git-send-email-festevam@gmail.com>
Hello,
On Mon, 13 Mar 2017 13:26:21 -0300, Fabio Estevam wrote:
> Bump kmscube version to fix build failures such as this one seen on sparc64:
> http://autobuild.buildroot.net/results/d7e/d7e82c67e0b04b0aea990bfb19dd6e4fd914bebe/build-end.log
>
> ,and also the one reported by Gary Bisson with Linaro 2017.02 ARM
> gnueabihf toolchain.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> package/kmscube/kmscube.hash | 2 +-
> package/kmscube/kmscube.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-14 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 16:26 [Buildroot] [PATCH] kmscube: bump version to fix build failures Fabio Estevam
2017-03-13 16:48 ` Gary Bisson
2017-03-14 22:42 ` 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=20170314234203.5e3d0194@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