From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] config_distro_bootcmd.h: add note on error handling
Date: Wed, 11 Mar 2015 10:22:23 -0600 [thread overview]
Message-ID: <55006BBF.7040009@wwwdotorg.org> (raw)
In-Reply-To: <20150311155119.GQ32541@bill-the-cat>
On 03/11/2015 09:51 AM, Tom Rini wrote:
> On Tue, Mar 10, 2015 at 03:40:58PM -0600, Stephen Warren wrote:
>
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This should make it more clear why there appear to be C pre-processor
>> symbols in the file that contain mixed case. They're really error
>> messages.
>>
>> Suggested-by: Simon Glass <sjg@chromium.org>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Thanks. It looks like you usually apply the patches to this file rather
than acking it for someone else to take. Was your reviewed-by just a
hint you're waiting for e.g. Simon to review it too?
next prev parent reply other threads:[~2015-03-11 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 21:40 [U-Boot] [PATCH] config_distro_bootcmd.h: add note on error handling Stephen Warren
2015-03-11 15:51 ` Tom Rini
2015-03-11 16:22 ` Stephen Warren [this message]
2015-03-11 17:35 ` Tom Rini
2015-03-11 18:42 ` Simon Glass
2015-03-15 21:51 ` [U-Boot] " Tom Rini
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=55006BBF.7040009@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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