From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] dfu:cosmetic: Fix printf text for buffer overflow condition
Date: Wed, 11 Sep 2013 06:38:29 +0200 [thread overview]
Message-ID: <522FF3C5.5020609@denx.de> (raw)
In-Reply-To: <1378819765-20159-2-git-send-email-l.majewski@samsung.com>
Hello Lukasz,
Am 10.09.2013 15:29, schrieb Lukasz Majewski:
> Correct error message if overflow is detected.
>
> Change-Id: I8a915c7353d49822c046fbc36241237b370e6c98
> Signed-off-by: Lukasz Majewski<l.majewski@samsung.com>
> ---
> drivers/dfu/dfu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Tested on the dxr2 and rut board, so:
Tested-by: Heiko Schocher <hs@denx.de>
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2013-09-11 4:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 13:29 [U-Boot] [PATCH 0/4] dfu: Various fixes and code optimizations Lukasz Majewski
2013-09-10 13:29 ` [U-Boot] [PATCH 1/4] dfu:cosmetic: Fix printf text for buffer overflow condition Lukasz Majewski
2013-09-11 4:38 ` Heiko Schocher [this message]
2013-09-10 13:29 ` [U-Boot] [PATCH 2/4] dfu: Make maximum DFU file size equal to default DFU data buffer Lukasz Majewski
2013-09-11 4:38 ` Heiko Schocher
2013-09-10 13:29 ` [U-Boot] [PATCH 3/4] dfu: Find DFU alt setting number by passing its name Lukasz Majewski
2013-09-10 14:32 ` Marek Vasut
2013-09-10 15:13 ` Lukasz Majewski
2013-09-10 21:20 ` Marek Vasut
2013-09-11 4:42 ` Heiko Schocher
2013-09-11 7:16 ` Lukasz Majewski
2013-09-10 13:29 ` [U-Boot] [PATCH 4/4] dfu: Extract common DFU code to handle "dfu_alt_info" environment variable Lukasz Majewski
2013-09-11 4:39 ` Heiko Schocher
2013-09-11 7:19 ` Marek Vasut
2013-09-11 9:09 ` Lukasz Majewski
2013-09-11 10:04 ` Marek Vasut
2013-09-11 11:30 ` Lukasz Majewski
2013-09-11 11:52 ` Marek Vasut
2013-09-11 12:53 ` [U-Boot] [PATCH 4/4 v2] " Lukasz Majewski
2013-09-12 10:37 ` Marek Vasut
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=522FF3C5.5020609@denx.de \
--to=hs@denx.de \
--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