From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openal: bump version to 1.18.0
Date: Fri, 21 Jul 2017 15:55:28 +0200 [thread overview]
Message-ID: <20170721155528.018481e1@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 -----------------
When you drop patches, it's nice to have a slightly more descriptive
commit log that says why those patches are dropped. For some of them,
it's quite obvious, since they were backports from upstream commits
(0001, 0002, 0003 and 0004), but for some others, it's not really
obvious (patch 0005).
Is the patch 0005 now upstream and part of 1.18.0 ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-21 13:55 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 [this message]
2017-07-21 14:07 ` André Hentschel
2017-07-22 13:16 ` Thomas Petazzoni
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=20170721155528.018481e1@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