From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [v2] powerpc/85xx: fix compatible property for the L2 cache node
Date: Sat, 30 Apr 2011 00:16:36 +0200 [thread overview]
Message-ID: <20110429221636.D08FFD5270C@gemini.denx.de> (raw)
In-Reply-To: <4DBB2723.4050408@freescale.com>
Dear Timur Tabi,
In message <4DBB2723.4050408@freescale.com> you wrote:
>
> I disagree. It's quite clear what I'm trying to do. I'm trying to insert a
This is your opinion. I disagree.
> NULL character into a string. Since device tree properties use a NULL to
> delimit multiple strings, it's clear that this is what the "0" is for.
Wrong data type. In C strings are _terminated_ by '\0' characters, so
using functions that are designed to deal with C strings are
obviously not the right tool to deal with data structures that have
_embedded_ NUL characters.
If you try, it quickly gets ugly like the code I rejected.
For example, who gives you any guarantee that sprintf() will continue
to append characters after it inserted the first NUL character?
A clever implementation could optimize this and return immediately
after seeing a NUL...
> Look at the original code:
>
> len = sprintf(compat_buf,
> "fsl,%c%s-l2-cache-controller",
> tolower(cpu->name[0]), cpu->name + 1);
>
> sprintf(&compat_buf[len + 1], "cache");
>
> I think my patch is clearer than this. In fact, because the original code was
> so obscure, there was a bug in it. I could have done this:
Why exactly do you think you have to use sprintf() to append a
constant string like "cache"?
If you want to make clean what's intended, then use something like
this:
len = sprintf(print_buf, "fsl,%c%s-l2-cache-controller",
tolower(cpu->name[0]), cpu->name + 1);
/* Include NUL characters */
memcpy(compat_buf, print_buf, len + 1);
memcpy(compat_buf + len + 1, "cache", sizeof("cache"));
If you want to optimize (I'm a fan of small memory footprint, but I'm
also a fan of readable code), use
len = sprintf(compat_buf, "fsl,%c%s-l2-cache-controller",
tolower(cpu->name[0]), cpu->name + 1);
/* Include NUL characters */
memcpy(compat_buf + len + 1, "cache", sizeof("cache"));
etc.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
egrep patterns are full regular expressions; it uses a fast determi-
nistic algorithm that sometimes needs exponential space.
- unix manuals
prev parent reply other threads:[~2011-04-29 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 14:58 [U-Boot] [PATCH] [v2] powerpc/85xx: fix compatible property for the L2 cache node Timur Tabi
2011-04-29 15:31 ` Kumar Gala
2011-04-29 20:33 ` Wolfgang Denk
2011-04-29 20:36 ` Kumar Gala
2011-04-29 20:40 ` Wolfgang Denk
2011-04-29 20:30 ` Wolfgang Denk
2011-04-29 20:44 ` Scott Wood
2011-04-29 20:55 ` Wolfgang Denk
2011-04-29 21:01 ` Timur Tabi
2011-04-29 22:16 ` Wolfgang Denk [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=20110429221636.D08FFD5270C@gemini.denx.de \
--to=wd@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