From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Alan Ott <alan@signal11.us>
Subject: Re: [PATCH] common: Make MENU depend on PROCESS_ESCAPE_SEQUENCE
Date: Tue, 22 May 2012 10:40:26 +0800 [thread overview]
Message-ID: <27196FB3-68EB-4583-9AF3-B256AE562D72@jcrosoft.com> (raw)
In-Reply-To: <20120521200614.GG30400@pengutronix.de>
Hi
Please revert break my work on at91bootstrap where we use the menu without any shell support
And the does work with or without hush support
Best Regards,
J.
On May 22, 2012, at 4:06 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Alan,
>
> On Mon, May 21, 2012 at 11:53:36AM -0400, Alan Ott wrote:
>> print_menu_entry() in common/menu.c depeneds on process_escape_sequence().
>>
>> Signed-off-by: Alan Ott <alan@signal11.us>
>
> Applied, thanks
>
> Sascha
>
>> ---
>> common/Kconfig | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/common/Kconfig b/common/Kconfig
>> index 73d620a..ebb9400 100644
>> --- a/common/Kconfig
>> +++ b/common/Kconfig
>> @@ -342,6 +342,7 @@ config AUTO_COMPLETE
>> config MENU
>> bool
>> prompt "Menu Framework"
>> + depends on PROCESS_ESCAPE_SEQUENCE
>> help
>> a menu framework that allow us to create list menu to simplify
>> barebox and make it more user-frendly
>> --
>> 1.7.0.4
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-05-22 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:53 Alan Ott
2012-05-21 20:06 ` Sascha Hauer
2012-05-22 2:40 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-05-22 3:35 ` Alan Ott
2012-05-21 22:44 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-22 2:22 ` [PATCH] common: Make HUSH_SHELL select PROCESS_ESCAPE_SEQUENCE Alan Ott
2012-05-22 3:32 ` [PATCH v2] common: Make MENU select PROCESS_ESCAPE_SEQUENCE if HUSH_SHELL is selected Alan Ott
2012-05-22 9:27 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-22 15:08 ` Alan Ott
2012-05-22 19:04 ` Sascha Hauer
2012-05-22 2:24 ` [PATCH] common: Make MENU depend on PROCESS_ESCAPE_SEQUENCE Alan Ott
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=27196FB3-68EB-4583-9AF3-B256AE562D72@jcrosoft.com \
--to=plagnioj@jcrosoft.com \
--cc=alan@signal11.us \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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