public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 0/8] Assorted patches
Date: Fri, 16 Feb 2018 09:52:16 +0100	[thread overview]
Message-ID: <cover.1518771143.git.jan.kiszka@siemens.com> (raw)

Flush of my remaining queue:
 - improvements for mount and umount
 - arm64 target
 - copyright and credit enhancements

Jan

Jan Kiszka (8):
  Mount devtmpfs read-only into chroot
  isar-events: Wait for failing umounts
  isar-events: Do not match on distro and arch
  Add Debian arm64 support to the core
  Add qemuarm64-stretch multiconfig
  Add qemuarm64-stretch to CI
  build-kernel.sh: Add copyright header
  Enhance credits

 README.md                                          |  2 +-
 meta-isar/conf/local.conf.sample                   |  1 +
 meta-isar/conf/machine/qemuarm64.conf              |  7 +++++
 meta-isar/conf/multiconfig/qemuarm64-stretch.conf  | 20 +++++++++++++
 meta-isar/recipes-core/images/files/setup.sh       | 18 +++++++++---
 meta/classes/dpkg-base.bbclass                     |  2 +-
 meta/classes/isar-events.bbclass                   | 34 +++++++++++++---------
 meta/recipes-devtools/buildchroot/buildchroot.bb   |  2 +-
 meta/recipes-devtools/buildchroot/files/setup.sh   | 18 +++++++++---
 .../isar-apt/files/distributions.in                |  2 +-
 meta/recipes-kernel/linux/files/build-kernel.sh    |  8 +++++
 scripts/ci_build.sh                                |  1 +
 12 files changed, 90 insertions(+), 25 deletions(-)
 create mode 100644 meta-isar/conf/machine/qemuarm64.conf
 create mode 100644 meta-isar/conf/multiconfig/qemuarm64-stretch.conf

-- 
2.13.6


             reply	other threads:[~2018-02-16  8:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  8:52 Jan Kiszka [this message]
2018-02-16  8:52 ` [PATCH 1/8] Mount devtmpfs read-only into chroot Jan Kiszka
2018-02-19 10:09   ` Consolidate mounting in tasks (was Re: [PATCH 1/8] Mount devtmpfs read-only into chroot) Claudius Heine
2018-02-20  6:38   ` [PATCH 1/8] Mount devtmpfs read-only into chroot Alexander Smirnov
2018-02-20  7:02     ` Alexander Smirnov
2018-02-20  7:03     ` Jan Kiszka
2018-02-20  8:18       ` Claudius Heine
2018-02-16  8:52 ` [PATCH 2/8] isar-events: Wait for failing umounts Jan Kiszka
2018-02-19  9:45   ` Alexander Smirnov
2018-02-19  9:48     ` Jan Kiszka
2018-02-19 10:03       ` Alexander Smirnov
2018-02-19 11:10         ` Jan Kiszka
2018-02-16  8:52 ` [PATCH 3/8] isar-events: Do not match on distro and arch Jan Kiszka
2018-02-19  9:54   ` Alexander Smirnov
2018-02-19 11:08     ` Jan Kiszka
2018-02-16  8:52 ` [PATCH 4/8] Add Debian arm64 support to the core Jan Kiszka
2018-02-16  8:52 ` [PATCH 5/8] Add qemuarm64-stretch multiconfig Jan Kiszka
2018-02-19 10:23   ` Alexander Smirnov
2018-02-19 11:15     ` Jan Kiszka
2018-02-19 12:19       ` Alexander Smirnov
2018-02-19 12:36         ` Jan Kiszka
2018-02-16  8:52 ` [PATCH 6/8] Add qemuarm64-stretch to CI Jan Kiszka
2018-02-16  8:52 ` [PATCH 7/8] build-kernel.sh: Add copyright header Jan Kiszka
2018-02-16  8:52 ` [PATCH 8/8] Enhance credits Jan Kiszka
2018-02-19 13:56 ` [PATCH 0/8] Assorted patches Alexander Smirnov
2018-02-19 14:08   ` Jan Kiszka
2018-02-19 14:19     ` Alexander Smirnov
2018-02-20 11:19 ` Alexander Smirnov

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.1518771143.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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