From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1] defaultenv-2: add bnet script to second stage barebox over net
Date: Tue, 4 Dec 2018 08:59:58 +0100 [thread overview]
Message-ID: <20181204075958.ormajl7wupxvdp4p@pengutronix.de> (raw)
In-Reply-To: <20181130150520.5876-1-o.rempel@pengutronix.de>
On Fri, Nov 30, 2018 at 04:05:20PM +0100, Oleksij Rempel wrote:
> Doing cycling barebox boot over the net is a good testing practice.
> It is possible to detect at least some bugs before flushing it to
> the system. Suddenly it looks like, it is done not oft enough. So, let's
> add this option mainline.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
Applied, thanks
Sascha
> defaultenv/defaultenv-2-base/boot/bnet | 5 +++++
> 1 file changed, 5 insertions(+)
> create mode 100644 defaultenv/defaultenv-2-base/boot/bnet
>
> diff --git a/defaultenv/defaultenv-2-base/boot/bnet b/defaultenv/defaultenv-2-base/boot/bnet
> new file mode 100644
> index 0000000000..1290a7acfc
> --- /dev/null
> +++ b/defaultenv/defaultenv-2-base/boot/bnet
> @@ -0,0 +1,5 @@
> +#!/bin/sh
> +
> +path="/mnt/tftp"
> +
> +global.bootm.image="${path}/${global.user}-barebox-${global.hostname}"
> --
> 2.19.1
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-12-04 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 15:05 Oleksij Rempel
2018-12-04 7:59 ` Sascha Hauer [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=20181204075958.ormajl7wupxvdp4p@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=o.rempel@pengutronix.de \
/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