Re: [U-Boot] [PATCH v2 0/9] Unified command execution in one place

2012-01-17 Thread Simon Glass
Hi Stefan, On Wed, Jan 11, 2012 at 11:43 PM, Stefan Roese wrote: > On Saturday 10 December 2011 19:43:52 Simon Glass wrote: >> At present two parsers have similar code to execute commands. Also >> cmd_usage() is called all over the place. This series adds a single >> function which processes comm

Re: [U-Boot] [PATCH v2 0/9] Unified command execution in one place

2012-01-11 Thread Stefan Roese
On Saturday 10 December 2011 19:43:52 Simon Glass wrote: > At present two parsers have similar code to execute commands. Also > cmd_usage() is called all over the place. This series adds a single > function which processes commands called cmd_process(). > > This new function understands return cod

Re: [U-Boot] [PATCH v2 0/9] Unified command execution in one place

2012-01-11 Thread Stefan Roese
Hi Simon, On Thursday 12 January 2012 05:37:00 Simon Glass wrote: > Hi, > > On Sat, Dec 10, 2011 at 10:43 AM, Simon Glass wrote: > > At present two parsers have similar code to execute commands. Also > > cmd_usage() is called all over the place. This series adds a single > > function which proce

Re: [U-Boot] [PATCH v2 0/9] Unified command execution in one place

2012-01-11 Thread Simon Glass
Hi, On Sat, Dec 10, 2011 at 10:43 AM, Simon Glass wrote: > At present two parsers have similar code to execute commands. Also > cmd_usage() is called all over the place. This series adds a single > function which processes commands called cmd_process(). > > This new function understands return co

[U-Boot] [PATCH v2 0/9] Unified command execution in one place

2011-12-10 Thread Simon Glass
At present two parsers have similar code to execute commands. Also cmd_usage() is called all over the place. This series adds a single function which processes commands called cmd_process(). This new function understands return codes, and in particular CMD_RET_USAGE to indicate a usage error. So r