All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Reyna <david.reyna@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/2] toaster: broken custom.xml and threads patch
Date: Mon, 28 May 2018 20:26:49 -0700	[thread overview]
Message-ID: <cover.1527564213.git.David.Reyna@windriver.com> (raw)

From: David Reyna <David.Reyna@windriver.com>

The Toaster for Rocko is broken on HEAD. There are two patches that made it into master and Sumo, but missed Rocko.

The first patch fixes an error that breaks the initialization of Toaster.
The second patches fixes a change in behaviour for Django that creates an extra thread that blocks Toaster from shutting down.

The following changes since commit 7e7ee662f5dea4d090293045f7498093322802cc:

  build-appliance-image: Update to rocko head revision (2018-05-23 17:46:34 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib dreyna/submit/dreyna/toaster/broken_customxml_threads_12751_patch
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=dreyna/submit/dreyna/toaster/broken_customxml_threads_12751_patch

David Reyna (2):
  bitbake: toaster: do not fail on optional 'custom.xml' file
  bitbake: Toaster: fix shutdown and extra threads

 bin/toaster                                                 | 4 ++--
 lib/toaster/bldcontrol/management/commands/checksettings.py | 5 ++++-
 2 files changed, 6 insertions(+), 3 deletions(-)

-- 
1.9.1



             reply	other threads:[~2018-05-29  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  3:26 David Reyna [this message]
2018-05-29  3:26 ` [PATCH 1/2] bitbake: toaster: do not fail on optional 'custom.xml' file David Reyna
2018-05-29  3:26 ` [PATCH 2/2] bitbake: Toaster: fix shutdown and extra threads David Reyna
2018-05-29 14:22 ` [PATCH 0/2] toaster: broken custom.xml and threads patch akuster808

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.1527564213.git.David.Reyna@windriver.com \
    --to=david.reyna@windriver.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.