From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-numpy: bump to version 1.16.2
Date: Sun, 17 Mar 2019 11:14:24 +0100 [thread overview]
Message-ID: <20190317111424.2a66d695@windsurf> (raw)
In-Reply-To: <20190316114943.14110-1-fontaine.fabrice@gmail.com>
On Sat, 16 Mar 2019 12:49:43 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Update patches and send them upstream
> - Update license hash (typos fixed and year updated)
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> .../0001-Don-t-use-fenv.h-on-uClibc.patch | 30 +++++++++++++
> package/python-numpy/0001-no-fenv-on-uclibc.patch | 49 ----------------------
> ...2-FIX-no-FPU-exceptions-bits-on-ARC-glibc.patch | 31 ++++++++++++++
> .../0003-no-FPU-exceptions-bits-on-ARC-glibc.patch | 42 -------------------
> package/python-numpy/python-numpy.hash | 6 +--
> package/python-numpy/python-numpy.mk | 2 +-
> 6 files changed, 65 insertions(+), 95 deletions(-)
> create mode 100644 package/python-numpy/0001-Don-t-use-fenv.h-on-uClibc.patch
> delete mode 100644 package/python-numpy/0001-no-fenv-on-uclibc.patch
> create mode 100644 package/python-numpy/0002-FIX-no-FPU-exceptions-bits-on-ARC-glibc.patch
> delete mode 100644 package/python-numpy/0003-no-FPU-exceptions-bits-on-ARC-glibc.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-17 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 11:49 [Buildroot] [PATCH 1/1] package/python-numpy: bump to version 1.16.2 Fabrice Fontaine
2019-03-17 10:14 ` Thomas Petazzoni [this message]
2019-07-11 21:38 ` Romain Naour
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=20190317111424.2a66d695@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox