From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] openal: Explicitly enable/disable NEON support
Date: Sun, 11 Sep 2016 13:55:13 +0200 [thread overview]
Message-ID: <20160911135513.23cebe29@free-electrons.com> (raw)
In-Reply-To: <9791f7f9-3928-8f8f-b68b-1d1c65639d27@dawncrow.de>
Hello,
On Sat, 10 Sep 2016 14:09:37 +0200, Andr? Hentschel wrote:
> Sorry was on a business trip.
> As it is upstream meanwhile (together with a runtime neon check suggested by you) I'm fine with a patch added to the openal package.
> It's your work, so be free to do so.
If you could send a Buildroot patch adding the upstream fix, it would
be nice.
> Or do you know about plans of an upcoming openal bugfix release?
> That'd be easier I guess
I'm not aware of upstream plans in terms of new releases, I don't know
if they do regular ones or not. In order to avoid seeing build
failures, backporting the upstreaming fix would be a good thing to do
for now.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-11 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 18:34 [Buildroot] [PATCH v2] openal: Explicitly enable/disable NEON support André Hentschel
2016-09-06 20:25 ` Thomas Petazzoni
2016-09-10 12:09 ` André Hentschel
2016-09-11 11:55 ` 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=20160911135513.23cebe29@free-electrons.com \
--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