From: "Anuj Mittal" <anuj.mittal@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.48][PATCH 0/3] Patch review request
Date: Wed, 24 Mar 2021 22:33:04 +0800 [thread overview]
Message-ID: <cover.1616596112.git.anuj.mittal@intel.com> (raw)
Please review these next set of changes for 1.48. Clean a-full on
autobuilder.
Thanks,
Anuj
The following changes since commit 7a6517243dbfecfd78f82f6709fbeaab2fb03e2c:
__init__.py: Fix bitbake debug log handling (2021-03-09 00:03:19 +0000)
are available in the Git repository at:
git://push.openembedded.org/bitbake-contrib stable/1.48-next
Jan Brzezanski (1):
Force parser shutdown after catching an exception
Richard Purdie (2):
runqueue: Fix task execution corruption issue
runqueue: Add setscene task overlap sanity check
lib/bb/cooker.py | 10 +++++-----
lib/bb/runqueue.py | 7 +++++++
2 files changed, 12 insertions(+), 5 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-24 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 14:33 Anuj Mittal [this message]
2021-03-24 14:33 ` [1.48][PATCH 1/3] runqueue: Fix task execution corruption issue Anuj Mittal
2021-03-24 14:33 ` [1.48][PATCH 2/3] runqueue: Add setscene task overlap sanity check Anuj Mittal
2021-03-24 14:33 ` [1.48][PATCH 3/3] Force parser shutdown after catching an exception Anuj Mittal
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.1616596112.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=bitbake-devel@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