From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: clarify kernel configuration entries
Date: Thu, 5 Mar 2015 21:18:50 +0100 [thread overview]
Message-ID: <20150305211850.0baf2e21@free-electrons.com> (raw)
In-Reply-To: <1425578112-7407-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Dear Vivien Didelot,
On Thu, 5 Mar 2015 12:55:12 -0500, Vivien Didelot wrote:
> 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>
Applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-05 20:18 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
2015-03-05 20:18 ` Thomas Petazzoni [this message]
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=20150305211850.0baf2e21@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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