From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] test: hexdump: fix misplaced return
Date: Wed, 12 Dec 2018 19:47:08 -0500 [thread overview]
Message-ID: <20181213004708.GJ8702@bill-the-cat> (raw)
In-Reply-To: <20181204203008.28843-1-simon.k.r.goldschmidt@gmail.com>
On Tue, Dec 04, 2018 at 09:30:08PM +0100, Simon Goldschmidt wrote:
> One of the hexdump tests in test/lib/hexdump.c returns right at the
> start of the function without testing anything.
>
> Fix this by moving the 'return 0;' statement to the end of the function.
>
> Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181212/1e69481e/attachment.sig>
prev parent reply other threads:[~2018-12-13 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 20:30 [U-Boot] [PATCH] test: hexdump: fix misplaced return Simon Goldschmidt
2018-12-05 12:55 ` Simon Glass
2018-12-09 20:53 ` Simon Goldschmidt
2018-12-11 1:07 ` Simon Glass
2018-12-13 0:47 ` Tom Rini [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=20181213004708.GJ8702@bill-the-cat \
--to=trini@konsulko.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