All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Sakoman <steve@sakoman.com>
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake][scarthgap][2.8][PATCH 0/4] Patch review
Date: Wed,  5 Mar 2025 14:09:25 -0800	[thread overview]
Message-ID: <cover.1741206585.git.steve@sakoman.com> (raw)

Please review this set of changes for 2.8/scarthgap and have comments back
by end of day Friday, March 7

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1127

The following changes since commit 4e443aeab9096b41c9e5ba41cd21027ecaa20285:

  bitbake-diffsigs: fix handling when finding only a single sigfile (2025-03-05 14:24:43 +0000)

are available in the Git repository at:

  https://git.openembedded.org/bitbake-contrib stable/2.8-nut
  https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-nut

Richard Purdie (4):
  utils: Print information about lock issue before exiting
  utils: Tweak lock_timeout logic
  utils: Add signal blocking for lock_timeout
  event/utils: Avoid deadlock from lock_timeout() and recursive events

 lib/bb/event.py | 10 +++++++++-
 lib/bb/utils.py | 20 +++++++++++++++++++-
 2 files changed, 28 insertions(+), 2 deletions(-)

-- 
2.43.0



             reply	other threads:[~2025-03-05 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 22:09 Steve Sakoman [this message]
2025-03-05 22:09 ` [bitbake][scarthgap][2.8][PATCH 1/4] utils: Print information about lock issue before exiting Steve Sakoman
2025-03-05 22:09 ` [bitbake][scarthgap][2.8][PATCH 2/4] utils: Tweak lock_timeout logic Steve Sakoman
2025-03-05 22:09 ` [bitbake][scarthgap][2.8][PATCH 3/4] utils: Add signal blocking for lock_timeout Steve Sakoman
2025-03-05 22:09 ` [bitbake][scarthgap][2.8][PATCH 4/4] event/utils: Avoid deadlock from lock_timeout() and recursive events Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2026-06-12 14:28 [bitbake][scarthgap][2.8][PATCH 0/4] Patch review Jeremy Rosen
2026-03-20  0:26 Yoann Congal
2024-10-30 19:12 Steve Sakoman

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.1741206585.git.steve@sakoman.com \
    --to=steve@sakoman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.