From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/9] Cleanup rootfs creation
Date: Wed, 15 May 2019 08:43:21 +0200 [thread overview]
Message-ID: <def4ac41-770b-3680-95f7-b01d710b4433@siemens.com> (raw)
In-Reply-To: <20190514180300.27164-1-mosipov@ilbers.de>
Hi Maxim,
On 14/05/2019 20.02, Maxim Yu. Osipov wrote:
> Hi,
>
> This is rebased version of v4 series against current 'next'.
Thx for the rebase. LGTM
regards,
Claudius
>
> Regards,
> Maxim.
>
> Claudius Heine (9):
> isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage
> isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to
> base.bbclass
> move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap
> buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH
> isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR
> bitbake.conf: remove unneeded and differently used variables
> image.bbclass: make IMAGE_ROOTFS overwritable
> bitbake.conf: set default QEMU_ARCH variables
> buildchroot/configscript: make creation of builder uid/gid idempotent
>
> meta-isar/conf/multiconfig/rpi-stretch.conf | 1 +
> meta/classes/base.bbclass | 9 +++++++++
> meta/classes/buildchroot.bbclass | 2 +-
> meta/classes/image-sdk-extension.bbclass | 2 +-
> meta/classes/image.bbclass | 2 +-
> meta/classes/isar-bootstrap-helper.bbclass | 18 ++----------------
> meta/conf/bitbake.conf | 13 ++++++++-----
> .../recipes-core/isar-bootstrap/isar-bootstrap-host.bb | 13 +++++--------
> .../isar-bootstrap/isar-bootstrap-target.bb | 6 +-----
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 1 +
> meta/recipes-devtools/buildchroot/buildchroot-host.bb | 3 ++-
> meta/recipes-devtools/buildchroot/buildchroot.inc | 3 +--
> .../recipes-devtools/buildchroot/files/configscript.sh | 4 ++--
> meta/recipes-devtools/sdkchroot/sdkchroot.bb | 5 ++---
> 14 files changed, 37 insertions(+), 45 deletions(-)
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-05-15 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 18:02 Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 6/9] bitbake.conf: remove unneeded and differently used variables Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 7/9] image.bbclass: make IMAGE_ROOTFS overwritable Maxim Yu. Osipov
2019-05-14 18:02 ` [PATCH v5 8/9] bitbake.conf: set default QEMU_ARCH variables Maxim Yu. Osipov
2019-05-14 18:03 ` [PATCH v5 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent Maxim Yu. Osipov
2019-05-15 6:43 ` Claudius Heine [this message]
2019-05-15 6:55 ` [PATCH v5 0/9] Cleanup rootfs creation Maxim Yu. Osipov
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=def4ac41-770b-3680-95f7-b01d710b4433@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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