From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v5 8/9] linux-mainline: Move cfg fragment test to debian/rules
Date: Tue, 22 Feb 2022 07:50:44 +0100 [thread overview]
Message-ID: <58e6aaf5-945d-d283-6c7d-18a478258003@siemens.com> (raw)
In-Reply-To: <20220213074111.23232-9-ubely@ilbers.de>
On 13.02.22 08:41, Uladzimir Bely wrote:
> From: Anton Mikanovich <amikan@ilbers.de>
>
> Perform all config fragments checking in Debian way.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> .../linux/linux-mainline_5.4.70.bb | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.70.bb b/meta-isar/recipes-kernel/linux/linux-mainline_5.4.70.bb
> index 980e137b..28e51c0d 100644
> --- a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.70.bb
> +++ b/meta-isar/recipes-kernel/linux/linux-mainline_5.4.70.bb
> @@ -25,11 +25,13 @@ LINUX_VERSION_EXTENSION = "-isar"
>
> # For testing purposes only
> dpkg_configure_kernel_append() {
> - if ! grep "# CONFIG_MTD is not set" ${S}/${KERNEL_BUILD_DIR}/.config && \
> - ! grep "# CONFIG_MTD_UBI 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"
> +cat << EOF | sed -i '/^override_dh_auto_build/ r /dev/stdin' ${S}/debian/rules
> + if ! grep "# CONFIG_MTD is not set" \$(O)/.config && \\
> + ! grep "# CONFIG_MTD_UBI is not set" \$(O)/.config; then \\
> + grep "# CONFIG_UBIFS_FS is not set" \$(O)/.config || \\
> + (echo "Self-check failed: CONFIG_UBIFS_FS still enabled" && exit 1); \\
> + fi
> + grep "CONFIG_ROOT_NFS=y" \$(O)/.config || \\
> + (echo "Self-check failed: CONFIG_ROOT_NFS not enabled" && exit 1)
> +EOF
> }
As commented on in patch 6: anti-pattern that we should avoid in Isar code.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-02-22 6:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 7:41 [PATCH v5 0/9] Avoid using shell environment during the build Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 1/9] template: Copy template attributes on transform Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 2/9] linux-module: Do not use shell environment Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 3/9] u-boot: " Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 4/9] trusted-firmware: " Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 5/9] optee-os: " Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 6/9] optee-os-stm32mp15x: " Uladzimir Bely
2022-02-22 6:49 ` Jan Kiszka
2022-02-22 12:29 ` Uladzimir Bely
2022-02-23 14:01 ` Jan Kiszka
2022-02-13 7:41 ` [PATCH v5 7/9] kselftest: " Uladzimir Bely
2022-02-13 7:41 ` [PATCH v5 8/9] linux-mainline: Move cfg fragment test to debian/rules Uladzimir Bely
2022-02-22 6:50 ` Jan Kiszka [this message]
2022-02-13 7:41 ` [PATCH v5 9/9] linux-custom: Move cfg fragments applying " Uladzimir Bely
2022-02-23 13:53 ` Henning Schild
2022-02-24 9:09 ` Uladzimir Bely
2022-02-24 12:36 ` Henning Schild
2022-02-24 14:49 ` Uladzimir Bely
2022-02-24 19:53 ` Henning Schild
2022-02-22 6:39 ` [PATCH v5 0/9] Avoid using shell environment during the build Anton Mikanovich
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=58e6aaf5-945d-d283-6c7d-18a478258003@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@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