All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/16] thud-next patch review
Date: Sun,  7 Apr 2019 14:54:20 +0530	[thread overview]
Message-ID: <cover.1554628807.git.akuster808@gmail.com> (raw)

There are the commit I intend on sending a pull request for in two days. Tuesday my timezone (IST)

Please provide feedback by then if there are any issues. This is mostly OEQA changes. They have been througt the AB a-full and passed.

The following changes since commit 45032e30be70503faeee468159b216031b729309:

  build-appliance-image: Update to thud head revision (2019-03-27 23:22:49 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/thud-nmut
  http://cgit.openembedded.org//log/?h=stable/thud-nmut

Armin Kuster (1):
  Revert "boost: update to 1.69.0"

Chen Qi (1):
  pkgdata.py: avoid target-sdk-dummy-provides to mess things up

Mazliana (1):
  oeqa/manual/bsp-hw.json: add non-IA tests

Richard Purdie (2):
  resulttool: Allow store to work on single files
  resulttool: Allow extraction of ptest data

Sudhir Sharma (1):
  oeqa/manual: Add manual runtime 'compliance' testcases to json

Yeoh Ee Peng (6):
  oeqa/manual/toaster: transfer manual toaster test cases to oeqa
  oeqa/manual/toaster: updated test id naming
  resulttool/manualexecution: Standardize input check
  resulttool/manualexecution: Enable display full steps without press
    enter
  resulttool/manualexecution: Fixed step sorted by integer
  resulttool/manualexecution: Refactor and simplify codebase

sangeeta jain (4):
  oeqa/manual/sdk.json: Updated toolchain tarball to core-image-sato
  oeqa/manual/bsp-hw.json: test id updated and obsolete test cases
    removed
  oeqa/manual/compliance-test.json: test id updated and missing test
    cases added
  oeqa/manual/kernel-dev.json: test id updated

 meta/lib/oeqa/manual/bsp-hw.json                   |  264 +-
 meta/lib/oeqa/manual/compliance-test.json          |  194 ++
 meta/lib/oeqa/manual/kernel-dev.json               |   36 +-
 meta/lib/oeqa/manual/sdk.json                      |   14 +-
 meta/lib/oeqa/manual/toaster-managed-mode.json     | 2572 ++++++++++++++++++++
 meta/lib/oeqa/manual/toaster-unmanaged-mode.json   | 1170 +++++++++
 meta/lib/oeqa/selftest/cases/pkgdata.py            |    1 +
 ...bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} |    0
 .../boost/{boost-1.69.0.inc => boost-1.68.0.inc}   |    4 +-
 meta/recipes-support/boost/boost.inc               |    1 +
 ...-arch-instruction-set-flags-we-do-that-o.patch} |   23 +-
 ...ucibility-add-file-directive-to-assembler.patch |  243 ++
 .../boost/{boost_1.69.0.bb => boost_1.68.0.bb}     |    6 +-
 scripts/lib/resulttool/manualexecution.py          |   61 +-
 scripts/lib/resulttool/resultutils.py              |   39 +-
 scripts/lib/resulttool/store.py                    |   23 +-
 16 files changed, 4467 insertions(+), 184 deletions(-)
 create mode 100644 meta/lib/oeqa/manual/compliance-test.json
 create mode 100644 meta/lib/oeqa/manual/toaster-managed-mode.json
 create mode 100644 meta/lib/oeqa/manual/toaster-unmanaged-mode.json
 rename meta/recipes-support/boost/{bjam-native_1.69.0.bb => bjam-native_1.68.0.bb} (100%)
 rename meta/recipes-support/boost/{boost-1.69.0.inc => boost-1.68.0.inc} (85%)
 rename meta/recipes-support/boost/boost/{0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch => 0003-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch} (93%)
 create mode 100644 meta/recipes-support/boost/boost/reproducibility-add-file-directive-to-assembler.patch
 rename meta/recipes-support/boost/{boost_1.69.0.bb => boost_1.68.0.bb} (56%)

-- 
2.7.4



             reply	other threads:[~2019-04-07  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07  9:24 Armin Kuster [this message]
2019-04-09 21:31 ` [PATCH 00/16] thud-next patch review Martin Jansa
2019-04-10 13:27   ` 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.1554628807.git.akuster808@gmail.com \
    --to=akuster808@gmail.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 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.