[PATCH V4 0/6] luv : Add the pstore self tests to LUV
by Megha Dey
This patchset adds the pstore self tests to LUV. Apart from the recipe, it
adds the related binaries, runner and a parser to the final LUV image. It
addresses the issue: https://github.com/01org/luv-yocto/issues/35.
We also compile and install the required test scripts for running these
selftests and add the configurations as a config fragment to the default
config values from v4.13 kernel.
These test cases check pstore behavior and are useful to avoid regressions
of pstore. Pstore is used across kernel crash, so these test cases are split
into three parts.
- pstore_tests: check pstore behavior before crash
- pstore_post_reboot_tests: check pstore behavior after crash and reboot
- pstore_crash_test: cause kernel crash and reboot
The pstore_test and the pstore_post_reboot_tests are the actual scripts
for testing pstore. On the other hand, the pstore_crash_test is to cause
kernel panic and reboot. In addition, there is a "common_tests" script which
includes utilities and test cases used commonly in these scripts.
When the pstore_crash_test is executed, it creates a file as a reboot flag.
The pstore_post_reboot_tests detects whether the file exists or not. If the
file doesn't exists, the test cases are skipped.
This test-suite will cause a reboot during its execution. The necesary
groundwork to ensure these type of test suites can be intergrated seamessly
into LUV has been included prior to introducing this patch series.
Changes v1->v2
1. fixed typos in commit message
2. Instead of hardcoding the path to save the LUV results, we pass it as a
parameter from the pstore-recipe to the pstore self tests
3. removed the umount /mnt/luv-storage in the pstore tests
Changes v2->v3
1. pstore_tests run even if luv.pstore-test is not given
2. Fixed stylistic issues in the pstore-test recipe
3. Added comments to clarify that reboot_dir variable needs to be updated if
the LUV_STORAGE variable ever changes in luv_test_manager
Changes v3->v4
1. Aligned some comments in pstore-test recipe.
Megha Dey (6):
linux-yocto-efi-test: Add a config fragment for pstore selftest
pstore-test: Add runner and luv-parser
pstore-test: Add pstore selftests recipe
linux-yocto-efi-test: pstore selftest reboot flag
luv: Enable pstore self tests
meta-luv/README: introduce luv.pstore-test parameter
meta-luv/README | 2 +
.../images/core-image-efi-initramfs.bb | 4 +-
.../luv-test/luv-test/luv-crash-handler | 8 ++-
meta-luv/recipes-core/pstore-test/pstore-test.bb | 83 ++++++++++++++++++++++
.../pstore-test/pstore-test/luv-parser-pstore-test | 41 +++++++++++
.../pstore-test/pstore-test/pstore-test-runner | 15 ++++
...001-selftests-change-reboot-flag-location.patch | 46 ++++++++++++
.../linux/linux-yocto-efi-test/pstore-test.cfg | 4 ++
.../linux/linux-yocto-efi-test_4.13.bb | 2 +
9 files changed, 201 insertions(+), 4 deletions(-)
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test.bb
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test/pstore-test-runner
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-selftests-change-reboot-flag-location.patch
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/pstore-test.cfg
--
1.9.1
4 years, 2 months
[PATCH V3 0/6] luv : Add the pstore self tests to LUV
by Megha Dey
This patchset adds the pstore self tests to LUV. Apart from the recipe, it
adds the related binaries, runner and a parser to the final LUV image. It
addresses the issue: https://github.com/01org/luv-yocto/issues/35.
We also compile and install the required test scripts for running these
selftests and add the configurations as a config fragment to the default
config values from v4.13 kernel.
These test cases check pstore behavior and are useful to avoid regressions
of pstore. Pstore is used across kernel crash, so these test cases are split
into three parts.
- pstore_tests: check pstore behavior before crash
- pstore_post_reboot_tests: check pstore behavior after crash and reboot
- pstore_crash_test: cause kernel crash and reboot
The pstore_test and the pstore_post_reboot_tests are the actual scripts
for testing pstore. On the other hand, the pstore_crash_test is to cause
kernel panic and reboot. In addition, there is a "common_tests" script which
includes utilities and test cases used commonly in these scripts.
When the pstore_crash_test is executed, it creates a file as a reboot flag.
The pstore_post_reboot_tests detects whether the file exists or not. If the
file doesn't exists, the test cases are skipped.
This test-suite will cause a reboot during its execution. The necesary
groundwork to ensure these type of test suites can be intergrated seamessly
into LUV has been included prior to introducing this patch series.
Changes v1->v2
1. fixed typos in commit message
2. Instead of hardcoding the path to save the LUV results, we pass it as a
parameter from the pstore-recipe to the pstore self tests
3. removed the umount /mnt/luv-storage in the pstore tests
Changes v2->v3
1. pstore_tests run even if luv.pstore-test is not given
2. Fixed stylistic issues in the pstore-test recipe
3. Added comments to clarify that reboot_dir variable needs to be updated if
the LUV_STORAGE variable ever changes in luv_test_manager
Megha Dey (6):
linux-yocto-efi-test: Add a config fragment for pstore selftest
pstore-test: Add runner and luv-parser
pstore-test: Add pstore selftests recipe
linux-yocto-efi-test: pstore selftest reboot flag
luv: Enable pstore self tests
meta-luv/README: introduce luv.pstore-test parameter
meta-luv/README | 2 +
.../images/core-image-efi-initramfs.bb | 4 +-
.../luv-test/luv-test/luv-crash-handler | 8 ++-
meta-luv/recipes-core/pstore-test/pstore-test.bb | 83 ++++++++++++++++++++++
.../pstore-test/pstore-test/luv-parser-pstore-test | 41 +++++++++++
.../pstore-test/pstore-test/pstore-test-runner | 15 ++++
...001-selftests-change-reboot-flag-location.patch | 46 ++++++++++++
.../linux/linux-yocto-efi-test/pstore-test.cfg | 4 ++
.../linux/linux-yocto-efi-test_4.13.bb | 2 +
9 files changed, 201 insertions(+), 4 deletions(-)
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test.bb
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test/luv-parser-pstore-test
create mode 100644 meta-luv/recipes-core/pstore-test/pstore-test/pstore-test-runner
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-selftests-change-reboot-flag-location.patch
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/pstore-test.cfg
--
1.9.1
4 years, 2 months
[PATCH V3 00/10] Updates after moving to pyro
by Megha Dey
The luv-yocto next branch now has been merged with the
1. poky repository commit 0fcbb4d ("GNU_MIRROR: switch from ftp to https")
as this the commit from which poky/pyro is branched out.
2. meta-oe commit ad0db12 ("wireguard: module install cleanup")
as this the commit from which meta-oe/pyro is branched out.
3. meta-oe commit 5e82995 ("opencv: disable broken Intel FP16 detection").
This is meta-oe/pyro.
A new pyro-next branch will be created shortly.
Now that LUV is using the Yocto Project pyro release, the following updates
are in keeping with all the latest changes in pyro:
* Update dhcp to v4.3.5
* Update systemd to v232
* Update qemu to v2.8.0
* Use a variable (EFI_LOADER_IMAGE) which would take different values
depending on the target architecture instead of hardcoding names.
* In pyro, 'grub-efi-' prefix was added to the file name of efi binary.
Hence, LUV also needs to update the name of grub efi binary accordingly.
* The linux-firmware do_install task tries to remove the netronome folder,
but bitbake complains that there is no such directory. For now, we have
created the netronome directory.
* Now that LUV has updated to pyro, the OVMF recipe is alreay present in
the meta layer. Hence, there is no longer the need for us to carry this
recipe in meta-luv.
* Update kexec-tools to 2.0.15 since starting with 4.12 kernels,
kexec-tools cannot load a crash kernel.
* After updating pyro, the environment variable PATH is sanitized such that
normal native binary paths are removed. Now, we need to explicitly specify
the path to the git proxy command, something which was automatically done
earlier. This has been documented in meta-luv/README.
* qemu only needs to have a run time dependency on OVMF but currently it
has a build time dependency on ovmf and ovmf has a dependency on qemu. This
manifests itself as a circular dependency. Hence, adding OVMF to the
run-time dependency list of QEMU.
Changes v1->v2
1. Added a patch which uses a variable to take different values
depending on the target architecture instead of hardcoding names.
2. Cited the commid ID with the commit message
3. Removed an empty line from commit message
Changes v2->v3
1. Updated commit messages for recipes that were updated
2. Added variables in luv_netboot.bb instead of hardcoding
3. updated the section numbers and the index of README
Megha Dey (10):
dhcp: Update to 4.3.5
systemd: Update to v232
qemu: Update to 2.8.0
luv: use variables instead of hardcoding names
luv: add grub-efi prefix to efi binary
linux-firmware: create a netronome folder
meta-luv: remove the ovmf recipe
kexec-tools: Update to 2.0.15
meta-luv/README: Document how to use git with a proxy
qemu: Add runtime dependency on OVMF
meta-luv/README | 39 +-
meta-luv/classes/luv-efi.bbclass | 51 +-
meta-luv/recipes-bsp/grub/grub_git.bbappend | 2 +-
.../recipes-connectivity/dhcp/dhcp_4.3.4.bbappend | 4 -
.../recipes-connectivity/dhcp/dhcp_4.3.5.bbappend | 4 +
meta-luv/recipes-core/images/luv-netboot-image.bb | 16 +-
...s-Force-tools-variables-to-host-toolchain.patch | 48 --
.../ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch | 110 ---
...0002-ovmf-update-path-to-native-BaseTools.patch | 32 -
...makefile-adjust-to-build-in-under-bitbake.patch | 39 -
meta-luv/recipes-core/ovmf/ovmf_git.bb | 121 ----
meta-luv/recipes-core/systemd/systemd_230.bbappend | 34 -
meta-luv/recipes-core/systemd/systemd_232.bbappend | 34 +
meta-luv/recipes-devtools/qemu/qemu_2.7.0.bbappend | 2 -
meta-luv/recipes-devtools/qemu/qemu_2.8.0.bbappend | 2 +
.../linux-firmware/linux-firmware_git.bbappend | 8 +
...nd-the-semantics-of-kexec_iomem_for_each_.patch | 78 --
.../0001-vmcore-dmesg-Define-_GNU_SOURCE.patch | 31 -
...01-x86-x86_64-Fix-format-warning-with-die.patch | 78 --
...eneralize-and-rename-get_kernel_stext_sym.patch | 194 -----
.../0002-ppc-Fix-format-warning-with-die.patch | 43 --
...0003-arm64-identify-PHYS_OFFSET-correctly.patch | 76 --
.../0004-arm64-kdump-identify-memory-regions.patch | 202 ------
...5-arm64-kdump-add-elf-core-header-segment.patch | 191 -----
...6-arm64-kdump-set-up-kernel-image-segment.patch | 137 ----
.../0007-arm64-kdump-set-up-other-segments.patch | 35 -
...-add-DT-properties-to-crash-dump-kernel-s.patch | 150 ----
...-kdump-Add-support-for-binary-image-files.patch | 52 --
.../kexec/kexec-tools/kexec-aarch64.patch | 801 ---------------------
meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb | 48 --
meta/recipes-kernel/kexec/kexec-tools_2.0.15.bb | 36 +
31 files changed, 151 insertions(+), 2547 deletions(-)
delete mode 100644 meta-luv/recipes-connectivity/dhcp/dhcp_4.3.4.bbappend
create mode 100644 meta-luv/recipes-connectivity/dhcp/dhcp_4.3.5.bbappend
delete mode 100644 meta-luv/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch
delete mode 100644 meta-luv/recipes-core/ovmf/ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch
delete mode 100644 meta-luv/recipes-core/ovmf/ovmf/0002-ovmf-update-path-to-native-BaseTools.patch
delete mode 100644 meta-luv/recipes-core/ovmf/ovmf/0003-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch
delete mode 100644 meta-luv/recipes-core/ovmf/ovmf_git.bb
delete mode 100644 meta-luv/recipes-core/systemd/systemd_230.bbappend
create mode 100644 meta-luv/recipes-core/systemd/systemd_232.bbappend
delete mode 100644 meta-luv/recipes-devtools/qemu/qemu_2.7.0.bbappend
create mode 100644 meta-luv/recipes-devtools/qemu/qemu_2.8.0.bbappend
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-kexec-exntend-the-semantics-of-kexec_iomem_for_each_.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-vmcore-dmesg-Define-_GNU_SOURCE.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0001-x86-x86_64-Fix-format-warning-with-die.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0002-ppc-Fix-format-warning-with-die.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0003-arm64-identify-PHYS_OFFSET-correctly.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0004-arm64-kdump-identify-memory-regions.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0005-arm64-kdump-add-elf-core-header-segment.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0006-arm64-kdump-set-up-kernel-image-segment.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0007-arm64-kdump-set-up-other-segments.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0008-arm64-kdump-add-DT-properties-to-crash-dump-kernel-s.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/0009-arm64-kdump-Add-support-for-binary-image-files.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools/kexec-aarch64.patch
delete mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb
create mode 100644 meta/recipes-kernel/kexec/kexec-tools_2.0.15.bb
--
1.9.1
4 years, 2 months
[PATCH] fwts: bump to v17.09.00
by Gayatri Kammela
Update FWTS to version v17.09.00
Signed-off-by: Gayatri Kammela <gayatri.kammela(a)intel.com>
---
meta-luv/recipes-core/fwts/fwts_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/fwts/fwts_git.bb b/meta-luv/recipes-core/fwts/fwts_git.bb
index bca34b560261..78c995e44452 100644
--- a/meta-luv/recipes-core/fwts/fwts_git.bb
+++ b/meta-luv/recipes-core/fwts/fwts_git.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://wiki.ubuntu.com/Kernel/Reference/fwts"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://src/main.c;beginline=1;endline=16;md5=31da590f3e9f3bd34dcdb9e4db568519"
-PV = "V17.08.00+git${SRCPV}"
+PV = "V17.09.00+git${SRCPV}"
-SRCREV = "d78a50cdaec3d3c67045b6db1eea4e4c349a1064"
+SRCREV = "7cc5c0823ec56859b0c8d91607befd8a151ec7f1"
SRC_URI = "git://kernel.ubuntu.com/hwe/fwts.git \
file://luv-parser-fwts \
"
--
2.7.4
4 years, 2 months
[PATCH V2] chipsec: bump to v1.3.3
by Megha Dey
Now that a new version of CHIPSEC is out, update our recipe accordingly.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/chipsec/chipsec_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/chipsec/chipsec_git.bb b/meta-luv/recipes-core/chipsec/chipsec_git.bb
index 888cab4..ece9f1a 100644
--- a/meta-luv/recipes-core/chipsec/chipsec_git.bb
+++ b/meta-luv/recipes-core/chipsec/chipsec_git.bb
@@ -15,8 +15,8 @@ SRC_URI = "git://github.com/chipsec/chipsec.git \
file://0001-Revert-fix-issue-with-building-driver-on-32bit-syste.patch \
"
-SRCREV="a82209970012e7835dc16f73af4b377f9f5329d7"
-PV="1.3.1"
+SRCREV="284cf0bed6b89eebb99d8625287bbdb0ca079515"
+PV="1.3.3"
DEPENDS = "virtual/kernel python-core nasm-native python-setuptools-native virtual/${TARGET_PREFIX}gcc-initial"
RDEPENDS_${PN} = "python python-shell python-stringold python-xml \
--
1.9.1
4 years, 2 months
[PATCH] chipsec: bump to v1.3.3
by Ricardo Neri
Now that a new version of CHIPSEC is out, update our recipe accordingly.
Signed-off-by: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
---
meta-luv/recipes-core/chipsec/chipsec_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/chipsec/chipsec_git.bb b/meta-luv/recipes-core/chipsec/chipsec_git.bb
index da1b77d..39a692c 100644
--- a/meta-luv/recipes-core/chipsec/chipsec_git.bb
+++ b/meta-luv/recipes-core/chipsec/chipsec_git.bb
@@ -15,8 +15,8 @@ SRC_URI = "git://github.com/chipsec/chipsec.git \
file://0001-Revert-fix-issue-with-building-driver-on-32bit-syste.patch \
"
-SRCREV="a82209970012e7835dc16f73af4b377f9f5329d7"
-PV="1.3.1"
+SRCREV="284cf0bed6b89eebb99d8625287bbdb0ca079515"
+PV="1.3.3"
DEPENDS = "virtual/kernel python-core nasm-native python-setuptools-native"
RDEPENDS_${PN} = "python python-shell python-stringold python-xml \
--
2.7.4
4 years, 2 months
[PATCH 0/3] kernel-efi-warnings: x86: detect machine check errors
by Ricardo Neri
x86 systems feature a mechanism to detect hardware (machine) errors such
as system bus errors, parity errors, cache errors and TLB errors. Linux
has support to detect this underlying mechanism and report the error in
the kernel message buffer.
Likewise, machine check errors can be originated by misconfigurations
done in firmware before booting the operating system.
This new tests aims x86 systems. Therefore, it must be skipped on other
CPU architectures. Thus, this series also adds functionality for kernel-
efi-warnings to skip unsupported tests.
A third patch adds flexibility to select the location and number of lines
from dmesg that are reported upon error detection.
Ricardo Neri (3):
kernel-efi-warnings: add support for skipped tests
kernel-efi-warnings: customize the number of leading and trailing
lines
kernel-efi-warnings: x86: detect machine check errors
.../kernel-efi-warnings/kernel-efi-warnings | 30 +++++++++++++++++++++-
.../luv-parser-kernel-efi-warnings | 5 ++++
2 files changed, 34 insertions(+), 1 deletion(-)
--
2.7.4
4 years, 2 months
[PATCH V3 0/5] luv: Prepare LUV for tests suites which reboot
by Megha Dey
This patch series will prepare LUV to run test-suites which cause a
reboot in a seamless manner. To ensure this, we have the following
changes:
1. Introduce a new KEXEC_APPEND variable as we require to use different
command line options for cases where the testsuites are supposed to cause
a reboot and cases where test-suites casues a reboot abruptly.
2. Separate runner loop and counting logic in luv_test_manager to ensure
that the counting is done only after all the tests have completed.
(including those which might cause a voluntary reboot)
3. Add a -a option to tee to ensure that instead of overwriting the
result file for the test suites which cause a reboot, it will append to it.
4. Create a file the first time LUV boots and store the LUV result folder name
into a variable; should there be a reboot because of any test-suite, we will
restore the LUV results folder name from this stored variable. Thus, we will
have just one results folder and append the post reboot results to it.
5. Ensure that after reboot, LUV runs from the test-suie that caused the
reboot.
For network boots, we do not have persistant storage available. Hence,
tests which reboot will not work in the same way as a disk boot. We would not
be able to append to the result files as they will be lost on a reboot.
Changes v1->v2
1. Used variable LUV_STORAGE instead of hardcoding
2. Used a more readable logic to find out the number of test-suites which
have completed execution.
Changes v2->v3
1. Fixed typos and wrapped long commit messages within 75 characters
2. Added a -q option to grep to avoid seeing the runner name in logs
3. changed back variable name to "suites" from "num_tests" as num_tests
could refer to both test suites or test cases
Megha Dey (5):
luv-crash-handler: Introduce a new KEXEC_APPEND variable
luv-test-manager: separate runner loop and counting
luv-test-manager: add a -a option to tee
luv-test-manager: Create a file the first time LUV boots.
luv-test-manager: Prepare LUV for tests suites which reboot
.../luv-test/luv-test/luv-crash-handler | 6 ++-
.../luv-test/luv-test/luv-test-manager | 49 +++++++++++++++++-----
2 files changed, 42 insertions(+), 13 deletions(-)
--
1.9.1
4 years, 2 months
[PATCH V2 0/6] Getting ready for pyro
by Megha Dey
Pyro is the latest release of the Yocto Project. Upcoming features
require us to have the latest and greatest code from the Yocto Project.
Also, it is also good as we get to have new features and security updates.
Unfortunately, this comes with some pain (lots of it). This patchset
prepares the meta-luv layer to be merged with pyro. The changes can be
summarized as follows:
* The old style bb.data.getVar API is obsolete. We have replaced the
bb.data.getVar accesses directly with the data store object.
* Both bits and grub-efi need to be only when the target architecture is
x86. Currently, luv tries to build these for all architectures. We have
made sure that they are being conditionally built only for x86 platforms.
* Build time dependencies do not require to use the ${PN} suffix. No other
recipes apart from some in meta-luv use this. We have removed this
suffix from the DEPENDS variable in all recipes in meta-luv.
* Building bits fails after updating to pyro. Including the sysmacros.h
header in some files resolves this error.
* From pyro onwards, sysroots are isolated to be per recipe. Thus, recipes
can now fail due to auto-detection of undeclared/missing dependencies. We
have explicitly added all the necessary dependencies to individual recipes
which were earlier assumed to be taken from the common sysroot.
* Till now, the sbsigntool recipe used the git fetcher. We were fetching
associated submodules in the do_configure task. Ideally, all sources should
be fetched in the do_fetch task. We have switched to the gitsm fetcher
which makes the code cleaner and is more coherant with other yocto recipes.
Changes v1->v2
1. Added a DEPENDS_append to state dendencies more clearly
2. updated commit message to cite the earlier commit mentioned
Megha Dey (6):
luv-efi: Don't use deprecated bb.data.getVar API
luv : build grub-efi/bits based on TARGET_ARCH
luv : Remove _${PN} suffix from DEPENDS variable
bits: include sysmacros.h to fix build error
luv: Switch to Recipe Specific Sysroots
sbsigntool: update fetcher from git to gitsm
meta-luv/classes/luv-efi.bbclass | 12 ++---
.../GRUB-util-include-sysmacros.h-header.patch | 51 ++++++++++++++++++++++
meta-luv/recipes-bsp/bits/bits_git.bb | 3 +-
meta-luv/recipes-bsp/shim-signed/shim-signed.bb | 2 +-
meta-luv/recipes-core/chipsec/chipsec_git.bb | 3 +-
meta-luv/recipes-core/fwts/fwts_git.bb | 6 ++-
meta-luv/recipes-core/images/luv-live-image.bb | 4 +-
meta-luv/recipes-core/images/luv-netboot-image.bb | 3 +-
meta-luv/recipes-core/ndctl/ndctl_git.bb | 2 +-
meta-luv/recipes-devtools/qemu/qemu_2.7.0.bbappend | 4 +-
.../recipes-devtools/sbsigntool/sbsigntool_git.bb | 11 +----
11 files changed, 76 insertions(+), 25 deletions(-)
create mode 100644 meta-luv/recipes-bsp/bits/bits/GRUB-util-include-sysmacros.h-header.patch
--
1.9.1
4 years, 2 months
[PATCH] ndctl: bump to version 58(v58)
by Megha Dey
LUV currently uses linux 4.13. The corresponding NDCTL version is
v58. Updating the SRCREV accordingly.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/recipes-core/ndctl/ndctl_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/ndctl/ndctl_git.bb b/meta-luv/recipes-core/ndctl/ndctl_git.bb
index 43b5ed5..2ddfc2a 100644
--- a/meta-luv/recipes-core/ndctl/ndctl_git.bb
+++ b/meta-luv/recipes-core/ndctl/ndctl_git.bb
@@ -11,7 +11,7 @@ HOMEPAGE = "https://git.kernel.org/cgit/linux/kernel/git/nvdimm/nvdimm.git/tree/
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=e66651809cac5da60c8b80e9e4e79e08"
-PV = "v57+git${SRCPV}"
+PV = "v58+git${SRCPV}"
RDEPENDS_${PN} = "nvdimm-test"
COMPATIBLE_HOST='(x86_64).*'
@@ -23,7 +23,7 @@ inherit module-base
SRC_URI += "git://github.com/pmem/ndctl.git"
SRC_URI += "file://luv-parser-ndctl"
SRC_URI += "file://ndctl_runner"
-SRCREV = "d685bff1ed574cc714ae3e47f9d913f1c074d2b2"
+SRCREV = "0a628fdf4fe58a283b16c1bbaa49bb28b1842bf9"
S = "${WORKDIR}/git"
DEPENDS = "virtual/kernel kmod udev"
--
1.9.1
4 years, 2 months
