From: "Bart vdr. Meulen" <bartvdrmeulen@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] kernel: Ignore config difference when using rootfs in kernel option
Date: Mon, 28 May 2012 14:42:37 +0200 [thread overview]
Message-ID: <1338208981-8681-11-git-send-email-bartvdrmeulen@gmail.com> (raw)
From: "Bart vdr. Meulen" <bartvdrmeulen@gmail.com>
When using a rootfs inside the kernel the config option CONFIG_INITRAMFS_SOURCE
is changed build time, ignore this when checking for differences
after running oldconfig.
This prevents a make failure when the source kernel.config is read-only,
preventing the copy back action that normally takes place when a
difference is detected.
Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
---
rules/kernel.make | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/rules/kernel.make b/rules/kernel.make
index 4a45a3f..e1e3a6a 100644
--- a/rules/kernel.make
+++ b/rules/kernel.make
@@ -111,16 +111,19 @@ ifdef KERNEL_INITRAMFS_SOURCE_y
endif
@$(call ptx/oldconfig, KERNEL)
- @diff -q -I "# [^C]" "$(KERNEL_DIR)/.config" "$(<)" > /dev/null || cp "$(KERNEL_DIR)/.config" "$(<)"
-
#
+# CONFIG_INITRAMFS_SOURCE has been changed in .config, ignore when taking diff.
# Don't keep the expanded path to INITRAMS_SOURCE in $(KERNEL_CONFIG),
# because it contains local workdir path which is not relevant to
# other developers.
#
ifdef KERNEL_INITRAMFS_SOURCE_y
+ @diff -q -I "# [^C]" -I "^CONFIG_INITRAMFS_SOURCE=[^C]" "$(KERNEL_DIR)/.config" "$(<)" > /dev/null || \
+ cp "$(KERNEL_DIR)/.config" "$(<)"
@sed -i -e 's,^CONFIG_INITRAMFS_SOURCE.*$$,CONFIG_INITRAMFS_SOURCE=\"# Automatically set by PTXDist\",g' \
"$(<)"
+else
+ @diff -q -I "# [^C]" "$(KERNEL_DIR)/.config" "$(<)" > /dev/null || cp "$(KERNEL_DIR)/.config" "$(<)"
endif
@$(call touch)
--
1.7.9.5
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-05-28 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 12:42 Bart vdr. Meulen [this message]
2012-05-30 16:23 ` Michael Olbrich
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=1338208981-8681-11-git-send-email-bartvdrmeulen@gmail.com \
--to=bartvdrmeulen@gmail.com \
--cc=ptxdist@pengutronix.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