From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] UBI: Fix compile error when CONFIG_UBI_SILENCE_MSG defined
Date: Mon, 4 Jan 2016 08:04:51 +0100 [thread overview]
Message-ID: <568A1993.7060901@denx.de> (raw)
In-Reply-To: <20160103210503.GA32297@localhost.localdomain>
Hello Ladislav Michl
Am 03.01.2016 um 22:05 schrieb Ladislav Michl:
> drivers/mtd/ubi/io.c:1354:3: error: 'dump_len' undeclared (first use in
> this function)
> dump_len = max_t(int, 128, len - i);
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> ---
> drivers/mtd/ubi/io.c | 1 -
> 1 file changed, 1 deletion(-)
You sended this patch twice? Old version here:
http://patchwork.ozlabs.org/patch/561670/
removed this patch from patchwork.
bye,
Heiko
>
> diff --git a/drivers/mtd/ubi/io.c b/drivers/mtd/ubi/io.c
> index d1bdec3..0be9c5a 100644
> --- a/drivers/mtd/ubi/io.c
> +++ b/drivers/mtd/ubi/io.c
> @@ -1351,7 +1351,6 @@ static int self_check_write(struct ubi_device *ubi, const void *buf, int pnum,
> ubi_err(ubi, "self-check failed for PEB %d:%d, len %d",
> pnum, offset, len);
> ubi_msg(ubi, "data differ at position %d", i);
> - dump_len = max_t(int, 128, len - i);
> ubi_msg(ubi, "hex dump of the original buffer from %d to %d",
> i, i + dump_len);
> print_hex_dump(KERN_DEBUG, "", DUMP_PREFIX_OFFSET, 32, 1,
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-01-04 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 1:43 [U-Boot] [PATCH] Fix compile error when CONFIG_UBI_SILENCE_MSG defined Ladislav Michl
2016-01-03 21:05 ` [U-Boot] [PATCH] UBI: " Ladislav Michl
2016-01-04 7:04 ` Heiko Schocher [this message]
2016-01-04 8:12 ` Heiko Schocher
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=568A1993.7060901@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