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 v2 11/13] linux-mainline: Avoid failing UBIFS test when defconfig does not support it
Date: Mon, 13 Jan 2020 09:28:16 +0100	[thread overview]
Message-ID: <cfa53dafeb92f98ca8f086cdd2aaabcaf54af29d.1578904098.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1578904098.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1578904098.git.jan.kiszka@siemens.com>

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

Will be relevant for RISC-V.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

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 cb4d5e33..3c5335e8 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
@@ -28,8 +28,10 @@ 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"
+    if ! grep "# CONFIG_MTD is not set" ${S}/${KERNEL_BUILD_DIR}/.config; then
+        grep "# CONFIG_UBIFS_FS is not set" ${S}/${KERNEL_BUILD_DIR}/.config || \
+            bbfatal "Self-check failed: CONFIG_UBIFS_FS still enabled"
+    fi
     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:[~2020-01-13  8:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13  8:28 [PATCH v2 00/13] RISC-V support Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 01/13] meta: Add debian-sid-ports distro config Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 02/13] meta: Add RISC-V architecture Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 03/13] meta: Allow cross-compilation for RISC-V Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 04/13] start_vm: Add RISC-V 64-bit support Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 05/13] meta-isar: Add qemuriscv64 virtual target Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 06/13] meta-isar: Clean up qemu multiconfigs Jan Kiszka
2020-01-28 21:51   ` Henning Schild
2020-01-28 22:06     ` Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 07/13] u-boot-script: Account for variations of kernel files and boot commands Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 08/13] linux-custom: Tune strip rule to cover vmlinux images as well Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 09/13] linux-custom: Add support for RISC-V Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 10/13] linux-modules: " Jan Kiszka
2020-01-13  8:28 ` Jan Kiszka [this message]
2020-01-13  8:28 ` [PATCH v2 12/13] linux-mainline: Update to 5.4.10 Jan Kiszka
2020-01-13  8:28 ` [PATCH v2 13/13] meta-isar: Add HiFive Unleashed board as physical RISC-V target Jan Kiszka
2020-01-28 11:31 ` [PATCH v2 00/13] RISC-V support Jan Kiszka
2020-01-28 15:51   ` vijai kumar
2020-01-28 16:02     ` Jan Kiszka
2020-01-28 16:09       ` vijai kumar
2020-01-28 19:23       ` vijai kumar
2020-01-28 22:06         ` 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=cfa53dafeb92f98ca8f086cdd2aaabcaf54af29d.1578904098.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