From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 5/5] barebox: add option to specify config fragments
Date: Sat, 02 May 2015 14:55:47 +0200 [thread overview]
Message-ID: <5544C953.9030106@mind.be> (raw)
In-Reply-To: <1430231675-8613-5-git-send-email-bos@je-eigen-domein.nl>
On 28/04/15 16:34, Floris Bos wrote:
> Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> boot/barebox/Config.in | 6 ++++++
> boot/barebox/barebox.mk | 1 +
> 2 files changed, 7 insertions(+)
>
> diff --git a/boot/barebox/Config.in b/boot/barebox/Config.in
> index 48431bd..dbe79e9 100644
> --- a/boot/barebox/Config.in
> +++ b/boot/barebox/Config.in
> @@ -91,6 +91,12 @@ config BR2_TARGET_BAREBOX_CUSTOM_CONFIG_FILE
> help
> Path to the barebox configuration file
>
> +config BR2_TARGET_BAREBOX_CONFIG_FRAGMENT_FILES
> + string "Additional configuration fragment files"
> + help
> + A space-separated list of configuration fragment files,
> + that will be merged to the main Barebox configuration file.
> +
> config BR2_TARGET_BAREBOX_BAREBOXENV
> bool "bareboxenv tool in target"
> help
> diff --git a/boot/barebox/barebox.mk b/boot/barebox/barebox.mk
> index 54f52bb..5095ffa 100644
> --- a/boot/barebox/barebox.mk
> +++ b/boot/barebox/barebox.mk
> @@ -60,6 +60,7 @@ BAREBOX_SOURCE_CONFIG = $(call qstrip,$(BR2_TARGET_BAREBOX_CUSTOM_CONFIG_FILE))
> endif
>
> BAREBOX_KCONFIG_FILE = $(BAREBOX_SOURCE_CONFIG)
> +BAREBOX_KCONFIG_FRAGMENT_FILES = $(call qstrip,$(BR2_TARGET_BAREBOX_CONFIG_FRAGMENT_FILES))
> BAREBOX_KCONFIG_EDITORS = menuconfig xconfig gconfig nconfig
> BAREBOX_KCONFIG_OPTS = $(BAREBOX_MAKE_FLAGS)
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2015-05-02 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:34 [Buildroot] [PATCH v2 1/5] kconfig-package: add support for config fragments Floris Bos
2015-04-28 14:34 ` [Buildroot] [PATCH v2 2/5] linux: add option to specify " Floris Bos
2015-05-02 10:39 ` Arnout Vandecappelle
2015-05-02 12:44 ` Arnout Vandecappelle
2015-05-06 4:16 ` Gergely Imreh
2015-04-28 14:34 ` [Buildroot] [PATCH v2 3/5] busybox: " Floris Bos
2015-05-02 12:47 ` Arnout Vandecappelle
2015-04-28 14:34 ` [Buildroot] [PATCH v2 4/5] uclibc: " Floris Bos
2015-05-02 12:55 ` Arnout Vandecappelle
2015-04-28 14:34 ` [Buildroot] [PATCH v2 5/5] barebox: " Floris Bos
2015-05-02 12:55 ` Arnout Vandecappelle [this message]
2015-05-02 10:37 ` [Buildroot] [PATCH v2 1/5] kconfig-package: add support for " Arnout Vandecappelle
2015-05-02 11:30 ` Floris Bos
2015-05-02 12:43 ` Arnout Vandecappelle
2015-05-06 4:14 ` Gergely Imreh
2015-05-21 21:52 ` Thomas Petazzoni
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=5544C953.9030106@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.