From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Franck JULLIEN <franck.jullien@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] (reformated) Allow board specific fancy banner
Date: Wed, 29 Dec 2010 12:36:52 +0100 [thread overview]
Message-ID: <20101229113652.GC14221@pengutronix.de> (raw)
In-Reply-To: <1293399652-2615-1-git-send-email-franck.jullien@gmail.com>
On Sun, Dec 26, 2010 at 10:40:52PM +0100, Franck JULLIEN wrote:
> This time I used git to send the email. I think I get it right.
> However, I didn't find how to put this file in the thread we were later...
> I don't think it is possible since those emails didn't have ID's to use with
> the In-Reply-To option (right ?).
--in-reply-to 'AANLkTik+7KJrf3H6ZW3i9pA115p2Gn=k=CXYHg5YJwRY@mail.gmail.com'
would have been the correct option.
And please put such infomal text after the tripple dash below, otherwise
it will end up in the commit log.
> ---
> common/Kconfig | 6 ++++++
> common/console.c | 10 ++++++++++
> 2 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/common/Kconfig b/common/Kconfig
> index 617f640..d46c8fc 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -248,6 +248,12 @@ config HUSH_FANCY_PROMPT
> Allow to set PS1 from the command line. PS1 can have several escaped commands
> like \h for CONFIG_BOARDINFO or \w for the current working directory.
>
> +config BOARD_BANNER
> + bool
> + prompt "allow a board specific fancy banner"
> + help
> + Allow to define a custom board banner (you must define BOARD_BANNER in your config.h)
The patch below seems to handle a missing BOARD_BANNER just fine, so
maybe s/must/can/.
Best regards
Uwe
> +
> config HUSH_GETOPT
> bool
> depends on SHELL_HUSH
> diff --git a/common/console.c b/common/console.c
> index 82786f2..8a830e3 100644
> --- a/common/console.c
> +++ b/common/console.c
> @@ -46,7 +46,17 @@ EXPORT_SYMBOL(console_list);
> static void display_banner (void)
> {
> printf (RELOC("\n\n%s\n\n"), RELOC_VAR(version_string));
> +#ifdef CONFIG_BOARD_BANNER
> +#ifdef BOARD_BANNER
> + printf(RELOC(BOARD_BANNER));
> +#else
> +#define VT100_YELLOW "\033[1;33m"
> +#define VT100_RESET "\033[1;0m"
> + printf(RELOC("Board: " VT100_YELLOW CONFIG_BOARDINFO VT100_RESET "\n"));
> +#endif
> +#else
> printf(RELOC("Board: " CONFIG_BOARDINFO "\n"));
> +#endif
> }
>
> static int __early_initdata initialized = 0;
> --
> 1.7.1
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-12-29 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 21:40 Franck JULLIEN
2010-12-27 6:43 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <AANLkTik6kuBviOejiXT_6eU2ZiaagDDMJy2Fsgc_6dk_@mail.gmail.com>
2010-12-28 6:33 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-29 11:36 ` Uwe Kleine-König [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=20101229113652.GC14221@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=franck.jullien@gmail.com \
/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