From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot: add default for BR2_TARGET_UBOOT_PATCH
Date: Wed, 22 Apr 2015 22:22:25 +0200 [thread overview]
Message-ID: <20150422222225.4b80a2bd@free-electrons.com> (raw)
In-Reply-To: <1429623936-4438-1-git-send-email-fhunleth@troodon-software.com>
Dear Frank Hunleth,
On Tue, 21 Apr 2015 09:45:36 -0400, Frank Hunleth wrote:
> Automatically copy over the value from BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR
> to make handling its deprecation easier. Thanks to Arnout for the
> suggestion.
>
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> boot/uboot/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/boot/uboot/Config.in b/boot/uboot/Config.in
> index 4f01499..419b183 100644
> --- a/boot/uboot/Config.in
> +++ b/boot/uboot/Config.in
> @@ -84,6 +84,7 @@ config BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR
>
> config BR2_TARGET_UBOOT_PATCH
> string "Custom U-Boot patches"
> + default BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR
> help
> A space-separated list of patches to apply to U-Boot.
> Each patch can be described as an URL, a local file path,
Does this actually works? I've tried removing BR2_TARGET_UBOOT_PATCH=""
from my .config, add BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR="foo bar", and
ran 'make menuconfig'. I was hoping to see "foo bar" in
BR2_TARGET_UBOOT_PATCH, but it wasn't the case. Am I missing something?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-22 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 13:45 [Buildroot] [PATCH] uboot: add default for BR2_TARGET_UBOOT_PATCH Frank Hunleth
2015-04-22 20:22 ` Thomas Petazzoni [this message]
2015-04-22 20:31 ` Frank Hunleth
2015-04-22 20:50 ` Arnout Vandecappelle
2015-04-24 19:02 ` Frank Hunleth
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=20150422222225.4b80a2bd@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