From: Sascha Hauer <s.hauer@pengutronix.de>
To: Seraphim Dolbilov <s.dlblv@ya.ru>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [HELP] Barebox porting
Date: Mon, 28 Jan 2019 09:46:15 +0100 [thread overview]
Message-ID: <20190128084615.ssynohnulsd4sjwi@pengutronix.de> (raw)
In-Reply-To: <61845721548425461@sas2-80cfc068821c.qloud-c.yandex.net>
On Fri, Jan 25, 2019 at 05:11:01PM +0300, Seraphim Dolbilov wrote:
> Hello, friends!
>
> I'm interested if there is any internal Barebox convention about
> return types and values of initcall functions. What shall return
> my initcall if I want to stop booting and display error message?
An error message will be printed whenever you return an initcall with an
error. barebox won't stop then, but instead continues. This is done to
be able to tell the user something went wrong without adding many
printfs. If your error is so severe that you can't continue you have to
use panic() instead.
Sascha
--
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
next prev parent reply other threads:[~2019-01-28 8:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:34 Seraphim Dolbilov
2019-01-21 14:28 ` Seraphim Dolbilov
2019-01-21 15:12 ` Sascha Hauer
2019-01-21 15:35 ` Seraphim Dolbilov
2019-01-21 16:35 ` Sam Ravnborg
2019-01-21 16:43 ` Seraphim Dolbilov
2019-01-22 6:33 ` Sascha Hauer
2019-01-22 14:07 ` Seraphim Dolbilov
2019-01-22 14:42 ` Sascha Hauer
2019-01-22 16:12 ` Seraphim Dolbilov
2019-01-23 9:11 ` Sascha Hauer
2019-01-23 10:01 ` Seraphim Dolbilov
2019-01-23 10:17 ` Sascha Hauer
2019-01-25 12:18 ` Seraphim Dolbilov
2019-01-25 14:11 ` Seraphim Dolbilov
2019-01-28 8:46 ` Sascha Hauer [this message]
2019-02-04 10:13 ` [HELP] DT isues Seraphim Dolbilov
2019-02-05 11:52 ` Sascha Hauer
2019-02-05 13:45 ` Seraphim Dolbilov
2019-01-28 8:44 ` [HELP] Barebox porting Sascha Hauer
[not found] <44943261547037040@iva5-750e13568e4d.qloud-c.yandex.net>
2019-01-09 12:40 ` Серафим Долбилов
2019-01-09 13:03 ` Sascha Hauer
2019-01-16 15:14 ` Серафим Долбилов
2019-01-16 15:37 ` Серафим Долбилов
2019-01-16 17:29 ` Sam Ravnborg
2019-01-16 17:28 ` Sam Ravnborg
2019-01-16 18:48 ` Antony Pavlov
2019-01-16 15:59 ` Серафим Долбилов
2019-01-17 7:59 ` Sascha Hauer
2019-01-17 12:44 ` Серафим Долбилов
2019-01-17 13:28 ` Sascha Hauer
2019-01-17 13:43 ` Roland Hieber
2019-01-17 14:48 ` Серафим Долбилов
2019-01-17 16:26 ` Sam Ravnborg
2019-01-17 21:06 ` Sascha Hauer
2019-01-18 15:01 ` Seraphim Dolbilov
2019-01-18 15:14 ` Sascha Hauer
2019-01-18 16:30 ` Seraphim Dolbilov
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=20190128084615.ssynohnulsd4sjwi@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.dlblv@ya.ru \
/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