| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since we use static UID/GID for all users and groups on the platform,
we run into the issue described in [1] (upstream on "master" branch),
since [2] started to generate the users/groups dynamically at build
time based on all sysusers.d framents (not only "systemd.conf" like in
previous releases).
So "systemd_create_users":
- is completly redundant for Enea Edge Runtime since we populate all
users and groups statically;
- breaks the build;
- won't be fixed upstream since Hardknott is already EOL;
- can't be omitted by pinning poky to a previous commit (lots of CVE
fixes are newer than [2] + some recipe SRC_URI were updated after
[2] was merged);
- is easy to just disable for the machines where we know we have static
UID/GID (this is why we apply the change in local.conf);
[1] https://git.yoctoproject.org/poky/commit/meta/classes/\
rootfs-postcommands.bbclass?id=a559a2cba9284a1531fbc402c6fda1c5a51259c1
[2] https://git.yoctoproject.org/poky/commit/meta/classes/\
rootfs-postcommands.bbclass?id=8eee0062a7a036d0594dff193995ac7914c6124b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Change-Id: Iac50346ced5aec29cda4561da85f2d4f50560f38
|
|
|
|
|
| |
Change-Id: Ifd4e494542db2468bb1efb500b8bd03af66929f0
Signed-off-by: Andreas Wellving <andreas.wellving@enea.com>
|
|
|
|
|
| |
Change-Id: I64898d5f1a524473a1719af0128e5f814f0bb29c
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
|
|
|
|
|
|
| |
Remove graphical and audio features from the distribution
Change-Id: Ic5d1628d6daca0bdbd5699d5520d7f206db38865
Signed-off-by: Dan Andresan <Dan.Andresan@enea.com>
|
|\
| |
| |
| | |
Change-Id: I1b1576f01045d4be17a18fe5f4a8fb612d38113a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SAMPLE_UEFI_SB_KEYS_DIR and SAMPLE_BOOT_KEYS_DIR are
defined in meta-secure-core/meta-signing-key/conf/layer.conf
using ${LAYERDIR}, which changes at each automatic build.
efitools and grub-efi recipes reference the 2 variables.
The variables values change at each build, and this causes
efitools and grub-efi to rebuild.
To avoid the rebuild, exclude the 2 variables from task
signatures.
Change-Id: Ib3c51c14fa1e516b64e16adbee09ab28f2f818a7
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
| |
| |
| |
| |
| | |
Change-Id: I6363d78023ded97865f93307408150c7f2f6bbda
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| | |
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
Change-Id: Ic7f02246a56515284b62281ea053d431b5eb68cb
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New groups and users:
-g - kvm: added by libvirt [2]
-g - render: added by systemd, after boot-up introduced in [1]
Removed groups and users:
-g and u - systemd-resolve and systemd-network:
both were only kept for backward compatibility, not needed anymore
-g - lock: systemd_246.9.bb no longer adds it in GROUPADD_PARAM,
unlike systemd version on 2.4.0-2
-g and u - polkitd: systemd_246.9.bb no longer adds polkit in
PACKAGECONFIG
-g and u - ntp: meta-enea-virtualization/recipes-enea/ntp-user-stub/\
ntp-user-stub_1.0.bb removed
-g - netdev: dbus_1.12.20.bb no longer adds netdev in GROUPADD_PARAM
Added systemd_246.9.bbappend to overwrite basic.conf.in
and add 'render' using GROUPADD_PARAM at build-time instead on boot-time
Add new groups/users in basic.conf.in using fixed ids, in sync with
<layer>/files/{group,passwd}
[1] https://github.com/systemd/systemd/commit/4e15a7343cb
[2] https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/\
commit/recipes-extended/libvirt?h=gatesgarth&id=b5b5defc78ea03c8
Change-Id: If1768a544c53552bf2eff1d8051830975ae0ed2f
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
| |\
| |/
|/|
| | |
Change-Id: I3dbb828abdc877f343ee2cc1d86cfa714593f918
|
| |
| |
| |
| |
| | |
Change-Id: I52ae3d7ba29d225711a55bad678f73390590b511
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ia340aa58508bb3fd211a2a8ec715f43756424d8a
Signed-off-by: Catalin Iova <Catalin.Iova@enea.com>
|
| |
| |
| |
| |
| |
| |
| | |
Change name into Enea Edge for build output files
Change-Id: I760411db66617f6eabc2041db42be24fc3633c33
Signed-off-by: Catalin Iova <Catalin.Iova@enea.com>
|
| |
| |
| |
| |
| | |
Change-Id: I2cd5cc806e9264151897124b2dae42752f102afb
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Temporary solution until we upgrade vcpe to python3
and remove python2 support!
python2 is out of support for long time,
read https://www.python.org/doc/sunset-python-2/
https://python3statement.org/ and if you really have to
temporarily use this, then set
I_SWEAR_TO_MIGRATE_TO_PYTHON3 to "yes"
Change-Id: If20d79fb4051633a941c368f71443ae9bf10ad6a
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Iccc5c24fe95e0f0a3cad70b9c400902787d45476
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OSTree handles the contents of /boot separately from the rest of the
filesystem, see [1].
By default, upstream yocto rootfs generation stores the following
artifacts in /boot:
- kernel-image (bzImage) as /boot/bzImage-...;
- multiple packages that deploy grub.cfg, grubenv and EFI binaries:
* dpkg -S /boot/efi/EFI/BOOT
shim, seloader, ovmf-pkcs7-efi, grub-efi, grub-bootconf, efitools
However, none of these are ever used in Enea Edge, due to the way our
initial installation and subsequent upgrade work:
* live image building copies the kernel image from yocto deploy dir,
EFI binaries from rootfs /boot (this patch changes this to also
copy from the yocto deploy dir "bootloader" dir for uniformity) to
the root of the hddimg image;
* Enea Edge Installer (via utils.sh) creates the ESP partition
and copies all artifacts from hddimg to ESP under /EFI/BOOT [2];
* (currently) subsequent upgrades do _not_ update the contents of the
ESP /EFI/BOOT directory after initial installation;
* subsequent upgrades copy the kernel and ostree-initramfs from OSTree
rootfs (from /usr/lib/modules where ostree-kernel package resides)
to the ESP for SELoader validation;
This flow leaves unused (duplicate) artifacts in the following path:
/ostree/boot.x/poky/<poky hash>/0/boot/
While the kernel-image package can be omitted from installation, since
ostree-kernel package already installs the same binaries in
/usr/lib/modules (where OSTree will look for it), the rest of the
packages (shim, seloader etc.) also install other files to the rootfs
(e.g. CLI tools) and/or are used by the live image (hddimg) build
process as sources when copying said artifacts to the hddimg image; so
we can't simply skip installing them inside the rootfs.
Also, we want non-SOTA artifacts (e.g. rootfs.ext4) to still contain
these artifacts.
So the only sensible solution to avoiding confusion and removing
unused artifacts from OSTree images is to remove them right before
creating the OSTree image.
While at it, add some ENEA-specific comment markers to our prepend/
append fragments to make them stand out.
[1] https://github.com/ostreedev/ostree/blob/v2020.8/docs/\
atomic-upgrades.md#the-ostreeboot-directory
[2] http://sestogerrit02/cgit/linux/meta-enea-virtualization.git/tree/
recipes-enea/nfv-installer/nfv-installer/utils.sh?h=rocko#n230
Change-Id: I470c1c3d19f301cae4b8fbe184aa2906d4a25ddf
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
meta-cloud-services/meta-openstack was used for its cloud-init recipe,
which has meanwhile been moved to meta-virtualization.
Change-Id: I05561cf7611a5a4de3d3a076b9c3ee0e3feea173
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
meta-intel and meta-updater both add "wic" to IMAGE_FSTYPES.
However, it is not correctly configured for Enea Edge and it is not
used, so let's just remove it.
This also removes some build time tasks, e.g. building systemd-boot
and their corresponding (unused) artifacts (systemd-bootx64.efi,
linuxx64.stub.efi) from the deploy dir.
Change-Id: Ib8e477bb7461708b6b7c74726a04a120b80d06d9
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- do not install initramfs-module-* scripts that we won't use, e.g.
initramfs-module-install, initramfs-module-install-efi; this
removes their unused dependencies (e.g. grub-pc, parted), making
the initramfs smaller;
Depends-on: I6ce592a609650f0528314c14e6a0a2a4984ba864
Change-Id: I59143aad9ae80ad4a9a7fcbfc066d4783bcf4f2a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| | |
Change-Id: Ic7ddb4b8eafb1196bbbbc5e54b6854b25336affc
Signed-off-by: Andreas Wellving <andreas.wellving@enea.com>
|
| |
| |
| |
| |
| |
| | |
Depends-on: I658c86f562743a50e5c078899e133e279b96027b
Change-Id: I7165753a5f609ef337fd1f0b450f055a5768059e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. EFI_PREFIX: Fix duplicate grubx64.efi binaries by aligning paths:
* by default, upstream meta-oe and meta-secure-core both install
grubx64.efi, but in different locations (/boot/EFI/BOOT vs
/boot/efi/EFI/BOOT) unless we explicitely override some vars to
align the 2 paths; use the old behavior (/boot/efi/EFI/BOOT),
as meta-secure-core has multiple recipes that reference it, while
meta-oe allows changing the path via a single var override;
* note that in an OSTree deployment, these paths don't even exist
on target, we explicity install grubx64.efi during Enea Edge
installation by copying grubx64.efi from /EFI/BOOT in hddimg;
2. live-vm-common: use ${EFI_FILES_PATH} instead of hardcoding it;
3. core-image-minimal-initramfs, enea-nfv-access: Blacklist
grub-common-extras package on x86-64 machines if OSTree is used;
Depends-On: I703b53fd09c5ed75731375414f3e711ec3dadc3e
Change-Id: I3735bc004ece62f94172108f2e7ed4596942deea
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
removed cloud-init-systemd package from VNF image since the
content of this package is included now in cloud-init
package.
/usr/lib/systemd folder which supposed to be part of
cloud-init-systemd is copied in cloud-init
package(by default poky copy /usr/lib in ${PN}).
So it result an empty folder which is not used to create
cloud-init-systemd package anymore.
Change-Id: I49a592f4a076df34f1d845a219d185b14722f80e
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- drop our class override that basically reverted the boot menu entry
order and used to make serial the first (default) boot entry instead
of graphical;
- unset GRUB_GFXSERIAL that creates 2 boot entries instead of one;
- extend APPEND to contain both tty0 (graphical) and ttyS0 (serial):
* ttyS0 is last, so it has priority for selection as /dev/console;
Change-Id: I9be029bfea00d9aca61527046fedbe30e7ec58c2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| | |
since it is building from kernel source tree
Change-Id: Iaaed6e3cb6d55b4f1db398def68344cc6d7de575
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 9eceb046982de3da1921d97cedf4a3393e875d9a.
Change-Id: I9f9eb70af6d6548f25f16f1031ba43bf298cb9e2
|
| |
| |
| |
| |
| | |
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Change-Id: I0de2153af16f32309afd96402366ab0bb3edbf85
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- qemucross-wrapper was added during the gatesgarth rebase as a
workaround and is not currently needed;
- grub-efi-native was added during the initial SOTA grub integration
and is no longer needed (fixed by adding the correct DEPENDS in the
grub-efi recipe);
Change-Id: Ib415fcd80dbcbccb6e25068abd1c5a6bbad3a460
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This was added as a workaround during the gatesgarth rebase and is
no longer needed.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Change-Id: I627c75b77d1fc2ec4fb6de9c45ac3712cce7966f
|
| |
| |
| |
| |
| |
| | |
This reverts commit 8a666dac9fce6e073c34768e3b8a80eaaedfd887.
Change-Id: I96ea9fc565974bd66a252e178a0615e1b4bc0e9e
|
| |
| |
| |
| |
| |
| |
| |
| | |
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Signed-off-by: Andreas Wellving <andreas.wellving@enea.com>
Change-Id: I8892684cf302edaca98f50448d424432545df8de
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These were added to all images inheriting sota.bbclass.
We don't use them, so spare some unexpected dependencies by removing
them.
[1] https://github.com/advancedtelematic/meta-updater/commit/3bb86635
Change-Id: I01334024b70c161d1614bf2e7296cd3f7146ee13
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Upstream meta-updater switched from initrd to initramfs in [1], so
the image format changed from ext4.gz to cpio.gz.
[1] https://github.com/advancedtelematic/meta-updater/commit/212d71d2
Change-Id: Ibb1239eeba319877624fc76209f733862f52cb35
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While at it, replace some hardcoded p7b extenstions with ${SB_FILE_EXT}
and vmlinuz references with the appropiate variable (upstream no longer
renames bzImage to vmlinuz in ISO root after [1]).
[1] https://git.yoctoproject.org/cgit.cgi/poky/commit/?id=b6e36c01977
Change-Id: I5ce414a2f281ff2f1aeb0e26f35608cd8750855d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- override_image_types_ostree.inc is no longer required;
- override_image_types_ota.inc is mostly superseded by upstream, except
the creation of /boot/grub as a symlink to /boot/loader
(note that /boot/grub2 is a real dir with /boot/grub2/grub.cfg being
a symlink to /boot/loader/grub.cfg - it would be quite
complicated to override the whole IMAGE_CMD_ota just to keep
symlinking the parent dir instead of grub.cfg directly); /boot/grub
should be a symlink so that /boot/grub/grubenv also points to
/boot/loader/grubenv); fold its contents into
enea-nfv-access-host-common.inc as it doesn't override a class anymore
Note: Previously, OSTree did not follow symlinks, so the symlink
/boot/grub2/grub.cfg was being overwritten with a real file,
this is no longer an issue.
Change-Id: I38ec2b3a791ef7068b97caa49010eee62b7f4aee
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While at it, remove one obsoleted workaround from do_image_otaimg:
grub:do_populate_sysroot was removed from do_image_otaimg
(do_image_ota_ext4) deps in [1].
[1] https://github.com/advancedtelematic/meta-updater/commit/850801c
Change-Id: I45f77010aa9cd62dec2e37b278539dc4d28605c5
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adding IMG_FSTYPES += "hddimg" must be done before inheriting core-image
(in enea-image-common.inc) to avoid parsing errors.
Further, override_grub-efi_secureboot.inc overrides some functions
brought in by adding hddimg image type, so adding it after the include
would render the override useless.
Change-Id: Id87fc69c5dd5d0de953fbe014f639d382c3714e8
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
|/
|
|
|
|
|
|
| |
This is an initial commit, containing quick fixes and hacks to allow
building the images. All these issues will be re-evaluated and fixed
properly in their own commits.
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
|
|
|
|
|
|
|
|
| |
Cannot set USERADD_ERROR_DYNAMIC to error as it breaks the build.
We need to be carefull when adding new users/groups, to also add
them to files/{groups,passwd}
Change-Id: I7ecfa9936af6319ced946e243cbe3bbcd23e8e4c
Signed-off-by: Matei Valeanu <Matei.Valeanu@enea.com>
|
|
|
|
|
|
|
| |
this was disabled from kernel source tree
Change-Id: I82ff784dae6d34de19966b61f194944dba2adbe9
Signed-off-by: Adrian Calianu <adrian.calianu@enea.com>
|
|
|
|
|
| |
Change-Id: Ia39f1767dead467c0c78a5da085e3fc191f1cd4b
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before NFVA 2.3.0, OSTree only checked for the existence of
/boot/grub2/grub.cfg, skipping creating grub.cfg if that file was not
present.
In NFVA 2.3.0, only /boot/grub/grub.cfg is created, leading to issues
when trying to downgrade to an older NFVA release.
To maintain backwards compatibility with OSTree versions that only
check the old path, create both /boot/{grub,grub2} as symlinks to the
loader directory managed by OSTree.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Change-Id: Ic2c89930794e4c9d3ee3b2468d1331e5d7f63834
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- initramfs: remove run-postinsts package, it has no purpose as there is
no package manager inside the initramfs;
- rootfs: remove run-postinsts if the package manager is DPKG/APT, since
it duplicates the existing dpkg-configure.service installed by the
dpkg recipe;
- rootfs: cleanup DPKG backup file 'status-old', it contains information
about packages before the final installation stages of the rootfs
build process (completely irrelevant for the end user), saves >500kB;
Change-Id: I6bd257d56805a3dfee4478c88977942e9f210afc
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
| |
Change-Id: I8c782ffdfb2d7dc4466bb21b83e40af2c0edfb0e
Signed-off-by: Dragos Ciprian Nedelcu <Dragos.Ciprian.Nedelcu@enea.com>
|
|
|
|
|
| |
Change-Id: I916fc13c7979e4ab9077ec3e43b67b3a5320b74c
Signed-off-by: Catalin Iova <Catalin.Iova@enea.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Fix an obviously broken link created during installation
This led to issues creating/editing the grubenv file during NFVA
installation calls to `grub-mkconfig`.
These errors were not observed before, since stderr was not logged
during the installation.
Also, the link was fixed later on, so subsequent calls to grub-*
utilities no longer complained about it; the error only happened
during the NFVA installation.
2. Unify expected locations of grub.cfg
Previously, there were 3 possible locations of grub.cfg used
throughout the layers/scripts:
- /boot/loader/grub.cfg - the proper location, used by NFVA installer
components, as well as ostree related tooling;
- /boot/grub/grub.cfg - used in some recipes, but not present on the
board currently. Also the expected default location of our current
grub-* utilites, since we build grub without an explicit
`--with-grubdir` configure argument, which defaults (guessing) to
the `PACKAGE` name, in our case `grub` (and not `grub2`);
- /boot/grub2/grub.cfg - used in OTA image scripts by linking it to
/boot/loader/grub.cfg - however the link is later converted into
a real file, ending up duplicating the real grub.cfg (although they
are identical content-wise, they might confuse the user);
To settle this confusion, we will keep only /boot/loader/grub.cfg as
the true configuration file and convert /boot/grub2 to a symlink
pointing at /boot/loader, while also renaming it to /boot/grub.
This has the benefit of "fixing" all grub-* tools which try to write
their configuration files to /boot/grub. An alternative for that would
be building grub2 with the configure flag `--with-grubdir=loader`, but
that might break other things, so a symlink for the traditional
/boot/grub is safer.
Before creating this link, `grub-editenv list` would not work without
explicitly providing the filepath of the `/boot/loader/grubenv` file,
which might not be obvious for the end user.
Also, before this link, `grub-mkconfig` required explicitly setting the
`-p` (prefix) to '/' while running on the target.
Both of these issues will be fixed with the new link.
Since our ostree version (2018.7) is quite old, it requires one backport
for it to also check for /boot/grub/grub.cfg and not only
/boot/grub2/grub.cfg. The backport will be handled in the
meta-enea-virtualiation layer, hence this change's dependency.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Depends-on: I6bdc80e08a272e1534dd63717348bfaa50807d93
Change-Id: If8a61c89200414922a3f36e6c8fca58d7d3b6495
|
|
|
|
|
| |
Change-Id: I2a103bd73f5daaea8357ff2c5094dc2dd7fdf193
Signed-off-by: Andreas Wellving <andreas.wellving@enea.com>
|
|
|
|
|
|
|
| |
This would add too much overhead when switching branches.
Change-Id: I9ca5dbd0530017fcdd29fcb1d7a061386c98350e
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|