From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] oe/utils.py: ThreadPool fixes and improvements
Date: Tue, 23 Jun 2015 11:49:52 -0500 [thread overview]
Message-ID: <cover.1435078109.git.anibal.limon@linux.intel.com> (raw)
The following changes since commit 6f4304e36df7e416643dd4a7ee3de096f21f1020:
bitbake: runqueue: Sanity check BB_NUMBER_THREADS (2015-06-23 11:57:58 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib alimon/oe-utils
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=alimon/oe-utils
Aníbal Limón (2):
oe/utils.py: Fix thread leakage in ThreadPool
oe/utils.py: Add support for init/end helper functions in
ThreadWorker.
meta/classes/sstate.bbclass | 5 +++--
meta/lib/oe/utils.py | 39 +++++++++++++++++++++++++++++++--------
2 files changed, 34 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2015-06-23 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 16:49 Aníbal Limón [this message]
2015-06-23 16:49 ` [PATCH 1/2] oe/utils.py: Fix thread leakage in ThreadPool Aníbal Limón
2015-06-23 16:49 ` [PATCH 2/2] oe/utils.py: Add support for init/end helper functions in ThreadWorker Aníbal Limón
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=cover.1435078109.git.anibal.limon@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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