From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] trinity: bump version to fix a build failure using Linux 3.19 headers
Date: Mon, 23 Feb 2015 12:28:04 +0100 [thread overview]
Message-ID: <20150223122804.17dcca08@free-electrons.com> (raw)
In-Reply-To: <1424640573-5274-1-git-send-email-fabio.porcedda@gmail.com>
Dear Fabio Porcedda,
On Sun, 22 Feb 2015 22:29:33 +0100, Fabio Porcedda wrote:
> bump to the following trinity repository commit:
>
> kvm: Add ifdef around IA64 ioctls.
> Fix build error.
>
> CC ioctls/kvm.o
> In file included from ioctls/kvm.c:8:0:
> ioctls/kvm.c:115:8: error: ?KVM_IA64_VCPU_GET_STACK? undeclared here (not in a function)
> IOCTL(KVM_IA64_VCPU_GET_STACK),
> ^
> include/ioctls.h:53:15: note: in definition of macro ?IOCTL?
> { .request = _request, .name = #_request, }
> ^
> ioctls/kvm.c:116:8: error: ?KVM_IA64_VCPU_SET_STACK? undeclared here (not in a function)
> IOCTL(KVM_IA64_VCPU_SET_STACK),
> ^
> include/ioctls.h:53:15: note: in definition of macro ?IOCTL?
> { .request = _request, .name = #_request, }
>
> IA64 ioctls were removed in Linux 3.19.
>
> Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com>
Applied to next, thanks.
I initially wondered if we shouldn't apply this to master, but since it
happens only with 3.19 kernel headers, and such option has only been
added in next, I indeed decided to apply this patch only to the next
branch.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-23 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 21:29 [Buildroot] [PATCH next] trinity: bump version to fix a build failure using Linux 3.19 headers Fabio Porcedda
2015-02-23 11:28 ` Thomas Petazzoni [this message]
2015-02-24 10:56 ` Fabio Porcedda
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=20150223122804.17dcca08@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