From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] opencv3: enable pthreads parallel for loops
Date: Thu, 12 Oct 2017 22:51:36 +0200 [thread overview]
Message-ID: <20171012225136.3a92bb33@windsurf.home> (raw)
In-Reply-To: <20170929204724.25507-1-bradford@density.io>
Hello,
On Fri, 29 Sep 2017 16:47:24 -0400, Bradford Barr wrote:
> From: bradford barr <bradford@density.io>
>
> The WITH_PTHREADS_PF option was errantly categorized as a Windows only option.
> WITH_PTHREADS_PF actually enables a parallelization framework that utilizes
> pthreads to optimize some inner for loops of different OpenCV operations. This
> optimization is available on any platform that has pthreads.
>
> Signed-off-by: bradford barr <bradford@density.io>
> ---
> package/opencv3/opencv3.mk | 1 -
> 1 file changed, 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-12 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 20:47 [Buildroot] [PATCH 1/1] opencv3: enable pthreads parallel for loops Bradford Barr
2017-10-12 20:51 ` 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=20171012225136.3a92bb33@windsurf.home \
--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