From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] fs/initramfs: refactor with fs/cpio
Date: Wed, 14 Mar 2012 18:29:18 +0100 [thread overview]
Message-ID: <201203141829.18938.arnout@mind.be> (raw)
In-Reply-To: <CAAXf6LUAB_peHpGDsgv6P3W3sQ3MOeKOvwNpR77YZgcvE4N6RA@mail.gmail.com>
On Wednesday 14 March 2012 15:19:33 Thomas De Schampheleire wrote:
> linux/linux.mk contains:
> $(if $(BR2_TARGET_ROOTFS_INITRAMFS),
> touch $(BINARIES_DIR)/rootfs.cpio
> $(call KCONFIG_ENABLE_OPT,CONFIG_BLK_DEV_INITRD,$(@D)/.config)
> $(call
> KCONFIG_SET_OPT,CONFIG_INITRAMFS_SOURCE,\"$(BINARIES_DIR)/rootfs.cpio\",$(@D)/.config)
> ...
>
> This means that this code will be executed, even if
> BR2_TARGET_ROOTFS_INITRAMFS is explicitly set to 'n'. This may not be
> a common case, but I think it is valid to do so (I do so).
I don't think it is valid to do so. There are many places where we
expect Kconfig booleans to be either unquoted 'y' or nothing. If you do
need to override a config variable (in local.mk or on the command line),
BR2_FOO= works well enough.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-14 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 21:16 [Buildroot] [PATCH 1/2] cpio: fix boot with dynamic /dev Arnout Vandecappelle
2011-09-06 21:16 ` [Buildroot] [PATCH 2/2] fs/initramfs: refactor with fs/cpio Arnout Vandecappelle
2011-09-27 21:23 ` Peter Korsgaard
2012-03-13 15:49 ` Thomas De Schampheleire
2012-03-13 16:15 ` Arnout Vandecappelle
2012-03-14 14:19 ` Thomas De Schampheleire
2012-03-14 17:29 ` Arnout Vandecappelle [this message]
2011-09-27 21:23 ` [Buildroot] [PATCH 1/2] cpio: fix boot with dynamic /dev Peter Korsgaard
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=201203141829.18938.arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.