From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 2/5] barebox: introduce barebox-package function
Date: Sun, 24 Apr 2016 17:54:43 +0200 [thread overview]
Message-ID: <20160424175443.2e0104f2@free-electrons.com> (raw)
In-Reply-To: <9431c910cd145263e04a01f0a332555b9212e22e.1461489060.git.pieter@boesman.nl>
Hello,
On Sun, 24 Apr 2016 11:18:44 +0200, Pieter Smith wrote:
> No functional changes: Introduces a barebox-package function towards re-use by
> a 2nd config build.
>
> Because the function is meant to be called from within a $(eval), all instances
> of '$' has to be escaped. I.e. rename '$' -> '$$'.
>
> Signed-off-by: Pieter Smith <pieter@boesman.nl>
> ---
> boot/barebox/barebox.mk | 125 ++++++++++++++++++++++++++++--------------------
> 1 file changed, 72 insertions(+), 53 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-24 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 9:18 [Buildroot] [PATCH v5 0/5] Support building a 2nd Barebox config Pieter Smith
2016-04-24 9:18 ` [Buildroot] [PATCH v5 1/5] barebox: support multi-image-build image selection Pieter Smith
2016-04-24 15:43 ` Thomas Petazzoni
2016-04-24 21:20 ` Pieter Smith
2016-04-24 9:18 ` [Buildroot] [PATCH v5 2/5] barebox: introduce barebox-package function Pieter Smith
2016-04-24 15:54 ` Thomas Petazzoni [this message]
2016-04-24 21:21 ` Pieter Smith
2016-04-24 9:18 ` [Buildroot] [PATCH v5 3/5] barebox: extract package name argument Pieter Smith
2016-04-24 15:54 ` Thomas Petazzoni
2016-04-24 21:21 ` Pieter Smith
2016-04-24 9:18 ` [Buildroot] [PATCH v5 4/5] barebox: support 2nd config build Pieter Smith
2016-04-24 15:58 ` Thomas Petazzoni
2016-04-24 16:52 ` Pieter Smith
2016-04-24 9:18 ` [Buildroot] [PATCH v5 5/5] beaglebone: adds barebox bootloader defconfig Pieter Smith
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=20160424175443.2e0104f2@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