From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: needs NPTL threading
Date: Sun, 20 Apr 2014 10:55:08 +0200 [thread overview]
Message-ID: <20140420105508.74108f37@skate> (raw)
In-Reply-To: <e7a6b270dba399ed52c5d6b04e9625b880347e0e.1397971843.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Sun, 20 Apr 2014 08:30:43 +0300, Baruch Siach wrote:
> Strictly speaking, linuxthreads (new) should be enough, since it includes
> pthread_barrier_* implementation. However, we currently have no clean way to
> distinguish between LT and LT.old.
>
> Fixes:
> http://autobuild.buildroot.net/results/66a/66a9d2c664e0a9b2b0c51b998c72c2ceda90ff9b/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/mesa3d/Config.in | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-20 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 5:30 [Buildroot] [PATCH] mesa3d: needs NPTL threading Baruch Siach
2014-04-20 8: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=20140420105508.74108f37@skate \
--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