From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openal: bump version to 1.18.0
Date: Sat, 22 Jul 2017 15:16:24 +0200 [thread overview]
Message-ID: <20170722151624.1a90e3d3@windsurf> (raw)
In-Reply-To: <1500644031-25581-1-git-send-email-nerv@dawncrow.de>
Hello,
On Fri, 21 Jul 2017 15:33:51 +0200, Andr? Hentschel wrote:
> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
> ---
> .../0001-Build-NEON-code-with-mfpu-neon.patch | 29 ----------
> ...heck-for-run-time-NEON-support-by-reading.patch | 67 ----------------------
> ...003-Properly-check-if-proc-cpuinfo-opened.patch | 24 --------
> ...k-if-mfpu-neon-is-available-for-compiling.patch | 47 ---------------
> .../openal/0005-Fix-detection-of-C11-atomics.patch | 53 -----------------
> package/openal/openal.hash | 2 +-
> package/openal/openal.mk | 2 +-
> 7 files changed, 2 insertions(+), 222 deletions(-)
> delete mode 100644 package/openal/0001-Build-NEON-code-with-mfpu-neon.patch
> delete mode 100644 package/openal/0002-Check-for-run-time-NEON-support-by-reading.patch
> delete mode 100644 package/openal/0003-Properly-check-if-proc-cpuinfo-opened.patch
> delete mode 100644 package/openal/0004-Check-if-mfpu-neon-is-available-for-compiling.patch
> delete mode 100644 package/openal/0005-Fix-detection-of-C11-atomics.patch
Applied to master after improving the commit log to explain the status
of the removed patches.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-22 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 13:33 [Buildroot] [PATCH] package/openal: bump version to 1.18.0 André Hentschel
2017-07-21 13:55 ` Thomas Petazzoni
2017-07-21 14:07 ` André Hentschel
2017-07-22 13:16 ` 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=20170722151624.1a90e3d3@windsurf \
--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