From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: clarify kernel configuration entries
Date: Thu, 5 Mar 2015 19:30:04 +0100 [thread overview]
Message-ID: <20150305183004.GC3944@free.fr> (raw)
In-Reply-To: <1425578112-7407-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Vivien, Thomas, All,
On 2015-03-05 12:55 -0500, Vivien Didelot spake thusly:
> Since BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE can either be a complete
> .config file or a defconfig file, it can be confusing to the user
> whether to choose BR2_LINUX_KERNEL_USE_DEFCONFIG or
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG.
>
> To avoid that confusion, clarify Kconfig entry messages for in-tree
> defconfig and custom (def)config files.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> linux/Config.in | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/linux/Config.in b/linux/Config.in
> index 95c847b..36d7691 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -140,10 +140,10 @@ choice
> default BR2_LINUX_KERNEL_USE_DEFCONFIG
>
> config BR2_LINUX_KERNEL_USE_DEFCONFIG
> - bool "Using a defconfig"
> + bool "Using an in-tree defconfig file"
>
> config BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG
> - bool "Using a custom config file"
> + bool "Using a custom (def)config file"
>
> endchoice
>
> @@ -161,6 +161,9 @@ config BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE
> help
> Path to the kernel configuration file
>
> + Note: this can be a defconfig file or a complete .config file,
> + which can later be saved back with make linux-update-(def)config.
> +
> #
> # Binary format
> #
> --
> 2.3.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-03-05 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:55 [Buildroot] [PATCH] linux: clarify kernel configuration entries Vivien Didelot
2015-03-05 18:30 ` Yann E. MORIN [this message]
2015-03-05 20:18 ` 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=20150305183004.GC3944@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox