From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Update libaio to 0.3.110
Date: Wed, 10 Feb 2016 22:52:59 +0100 [thread overview]
Message-ID: <56BBB13B.9060000@mind.be> (raw)
In-Reply-To: <1454719042-6185-2-git-send-email-alistair.francis@xilinx.com>
On 06-02-16 01:37, Alistair Francis wrote:
> Update libaio from 0.3.108 to 0.3.110. This adds AArch64 support.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> ---
> package/libaio/0001-arches.patch | 671 ---------------------------------------
> package/libaio/Config.in | 2 +-
> package/libaio/libaio.hash | 4 +-
> package/libaio/libaio.mk | 2 +-
> 4 files changed, 4 insertions(+), 675 deletions(-)
> delete mode 100644 package/libaio/0001-arches.patch
>
> diff --git a/package/libaio/0001-arches.patch b/package/libaio/0001-arches.patch
> deleted file mode 100644
> index c85568c..0000000
> --- a/package/libaio/0001-arches.patch
> +++ /dev/null
> @@ -1,671 +0,0 @@
> -Patch borrowed from OpenEmbedded, available at
> -recipes/libaio/libaio-0.3.106/00_arches.patch in their source
> -tree. The patch has been adapted to remove the ARM-related
> -definitions, since they have been merged in later versions of libaio.
> -
> -The patch adds various architecture specific definitions (syscall
> -number and macros) for m68k, MIPS, PA/RISC and Sparc. Amongst these,
> -Buildroot mostly only cares about MIPS, but it was just easier to take
> -the whole OpenEmbedded patch.
> -
> -Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Why did you remove this patch? As far as I can see, there is nothing upstream
that adds mips support. Or is syscall-generic good enough?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-10 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 0:37 [Buildroot] [PATCH 0/2] Add Xen target support Alistair Francis
2016-02-06 0:37 ` [Buildroot] [PATCH 1/2] Update libaio to 0.3.110 Alistair Francis
2016-02-10 21:52 ` Arnout Vandecappelle [this message]
2016-02-10 22:43 ` Alistair Francis
2016-02-11 8:34 ` Arnout Vandecappelle
2016-02-17 18:50 ` Alistair Francis
2016-02-06 0:37 ` [Buildroot] [PATCH 2/2] Add Xen 4.6 Alistair Francis
2016-02-10 22:13 ` Arnout Vandecappelle
2016-03-09 0:32 ` Alistair Francis
2016-03-06 14:36 ` Thomas Petazzoni
2016-03-09 0:34 ` Alistair Francis
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=56BBB13B.9060000@mind.be \
--to=arnout@mind.be \
--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