From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: support multiple image files
Date: Tue, 20 Jun 2017 18:58:45 +0200 [thread overview]
Message-ID: <20170620185845.41140a53@windsurf.lan> (raw)
In-Reply-To: <20170620153000.18263-1-m.niestroj@grinn-global.com>
Hello,
On Tue, 20 Jun 2017 17:30:00 +0200, Marcin Niestroj wrote:
> diff --git a/boot/barebox/barebox-aux/Config.in b/boot/barebox/barebox-aux/Config.in
> index ec3b97cb8..8f21a0c45 100644
> --- a/boot/barebox/barebox-aux/Config.in
> +++ b/boot/barebox/barebox-aux/Config.in
> @@ -32,7 +32,7 @@ config BR2_TARGET_BAREBOX_AUX_CONFIG_FRAGMENT_FILES
> config BR2_TARGET_BAREBOX_AUX_IMAGE_FILE
> string "Image filename"
Maybe change to:
string "Image file names"
> help
> - Name of the generated barebox image, which will be copied to
> + Name of the generated barebox images, which will be copied to
And this to:
Space-separated list of barebox images which will be copied to
the images directory.
> diff --git a/boot/barebox/barebox/Config.in b/boot/barebox/barebox/Config.in
> index 3d8d01456..d29e742d6 100644
> --- a/boot/barebox/barebox/Config.in
> +++ b/boot/barebox/barebox/Config.in
> @@ -33,7 +33,7 @@ config BR2_TARGET_BAREBOX_CONFIG_FRAGMENT_FILES
> config BR2_TARGET_BAREBOX_IMAGE_FILE
> string "Image filename"
> help
> - Name of the generated barebox image, which will be copied to
> + Name of the generated barebox images, which will be copied to
> the images directory.
And of course same here.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-06-20 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 15:30 [Buildroot] [PATCH] barebox: support multiple image files Marcin Niestroj
2017-06-20 16:58 ` 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=20170620185845.41140a53@windsurf.lan \
--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 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.