From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Fix a few problems with the command parsers
Date: Fri, 30 May 2014 14:59:18 -0400 [thread overview]
Message-ID: <20140530185918.GU5836@bill-the-cat> (raw)
In-Reply-To: <1400901095-29391-1-git-send-email-sjg@chromium.org>
On Fri, May 23, 2014 at 09:11:31PM -0600, Simon Glass wrote:
> In a few cases the behaviour of both the hush and built-in parsers seems
> incorrect. One such case was exposed by commit 1992dbf which attempted to
> execute a simple command using hush and get the correct return value.
> Further digging exposed the other problems.
Can you please rebase this on master again? I imagine it doesn't quite
apply again with the splitting out in main.c series that's applied now,
thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140530/dc8e6dc7/attachment.pgp>
next prev parent reply other threads:[~2014-05-30 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 3:11 [U-Boot] [PATCH 0/4] Fix a few problems with the command parsers Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 1/4] Add final result tests for run_command_list() Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 2/4] Fix itest mask overflow Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 3/4] Fix hush to give the correct return code for a simple command Simon Glass
2014-05-25 8:08 ` Stefan Herbrechtsmeier
2014-05-24 3:11 ` [U-Boot] [PATCH 4/4] Correct return code from builtin_run_command_list() Simon Glass
2014-05-30 18:59 ` Tom Rini [this message]
2014-05-30 19:16 ` [U-Boot] [PATCH 0/4] Fix a few problems with the command parsers Simon Glass
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=20140530185918.GU5836@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.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