From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mender: fix ioctl build failure on powerpc64le / power8
Date: Tue, 28 Aug 2018 21:56:50 +0200 [thread overview]
Message-ID: <20180828215650.7a620434@windsurf.home> (raw)
In-Reply-To: <20180828170153.42156-1-giulio.benetti@micronovasrl.com>
Hello,
On Tue, 28 Aug 2018 19:01:53 +0200, Giulio Benetti wrote:
> diff --git a/package/mender/0001-ioctl-allow-building-for-ppc64le.patch b/package/mender/0001-ioctl-allow-building-for-ppc64le.patch
> new file mode 100644
> index 0000000000..f8aeaae143
> --- /dev/null
> +++ b/package/mender/0001-ioctl-allow-building-for-ppc64le.patch
> @@ -0,0 +1,31 @@
> +From 0c15fedbfe962912c8ad5e16073f4fc5ad03797f Mon Sep 17 00:00:00 2001
> +From: Giulio Benetti <giulio.benetti@micronovasrl.com>
> +Date: Tue, 28 Aug 2018 18:48:22 +0200
> +Subject: [PATCH] ioctl: allow building for ppc64le
So you allow building for ppc64le...
> +ppc64le is not supported at the moment.
... but ppc64le is not supported ?
This commit message doesn't make much sense I'm afraid :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-28 19:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 17:01 [Buildroot] [PATCH] mender: fix ioctl build failure on powerpc64le / power8 Giulio Benetti
2018-08-28 17:12 ` Mirza Krak
2018-08-28 17:26 ` Giulio Benetti
2018-08-28 19:57 ` Thomas Petazzoni
2018-08-28 20:35 ` Giulio Benetti
2018-08-29 5:44 ` Angelo Compagnucci
2018-08-29 7:12 ` Thomas Petazzoni
2018-08-29 7:35 ` Peter Korsgaard
2018-08-29 9:39 ` Giulio Benetti
2018-08-29 9:49 ` Thomas Petazzoni
2018-08-29 9:56 ` Mirza Krak
2018-08-29 13:43 ` Peter Korsgaard
2018-08-28 19:56 ` Thomas Petazzoni [this message]
2018-08-28 20:34 ` Giulio Benetti
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=20180828215650.7a620434@windsurf.home \
--to=thomas.petazzoni@bootlin.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.