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 v6 5/5] linux-mainline: Test config fragments and LINUX_VERSION_EXTENSION
Date: Wed, 18 Dec 2019 20:11:04 +0100	[thread overview]
Message-ID: <92b21f46919c5e865fe057fbf330cfb5ab40cc92.1576696264.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1576696264.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1576696264.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

Covers both the case of successful application as well as suppressed one
via "apply=no". And it sets a non-empty local version to stress the
default-off path.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg     |  1 +
 meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg     |  1 +
 meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb | 15 ++++++++++++++-
 3 files changed, 16 insertions(+), 1 deletion(-)
 create mode 100644 meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg
 create mode 100644 meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg

diff --git a/meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg b/meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg
new file mode 100644
index 00000000..97ec48c1
--- /dev/null
+++ b/meta-isar/recipes-kernel/linux/files/no-root-nfs.cfg
@@ -0,0 +1 @@
+# CONFIG_ROOT_NFS is not set
diff --git a/meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg b/meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg
new file mode 100644
index 00000000..72c1f7a4
--- /dev/null
+++ b/meta-isar/recipes-kernel/linux/files/no-ubifs-fs.cfg
@@ -0,0 +1 @@
+# CONFIG_UBIFS_FS is not set
diff --git a/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb b/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
index 695eb391..cb4d5e33 100644
--- a/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
+++ b/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
@@ -11,7 +11,10 @@ ARCHIVE_VERSION = "${@ d.getVar('PV')[:-2] if d.getVar('PV').endswith('.0') else
 
 SRC_URI += " \
     https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-${ARCHIVE_VERSION}.tar.xz \
-    file://x86_64_defconfig"
+    file://x86_64_defconfig \
+    file://no-ubifs-fs.cfg \
+    file://no-root-nfs.cfg;apply=no"
+
 SRC_URI[sha256sum] = "c1923b6bd166e6dd07be860c15f59e8273aaa8692bc2a1fce1d31b826b9b3fbe"
 
 SRC_URI_append_de0-nano-soc = " \
@@ -20,3 +23,13 @@ SRC_URI_append_de0-nano-soc = " \
 S = "${WORKDIR}/linux-${ARCHIVE_VERSION}"
 
 KERNEL_DEFCONFIG_qemuamd64 = "x86_64_defconfig"
+
+LINUX_VERSION_EXTENSION = "-isar"
+
+# For testing purposes only
+dpkg_configure_kernel_append() {
+    grep "# CONFIG_UBIFS_FS is not set" ${S}/${KERNEL_BUILD_DIR}/.config || \
+        bbfatal "Self-check failed: CONFIG_UBIFS_FS still enabled"
+    grep "CONFIG_ROOT_NFS=y" ${S}/${KERNEL_BUILD_DIR}/.config || \
+        bbfatal "Self-check failed: CONFIG_ROOT_NFS not enabled"
+}
-- 
2.16.4


  parent reply	other threads:[~2019-12-18 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 19:10 [PATCH v6 0/5] linux-custom recipe rework Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 1/5] recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 2/5] linux-mainline: fix stripping of .0 from the kernel version Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 3/5] linux-mainline: update from 4.19.0 to 4.19.88 Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb Jan Kiszka
2019-12-18 19:11 ` Jan Kiszka [this message]
2019-12-26 15:51 ` [PATCH v6 0/5] linux-custom recipe rework Baurzhan Ismagulov
2020-01-31  8:57 ` Henning Schild
2020-01-31  9:04   ` Jan Kiszka

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=92b21f46919c5e865fe057fbf330cfb5ab40cc92.1576696264.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