All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_fdt.c: fix parse of byte streams and strings
Date: Fri, 11 Sep 2009 12:56:49 -0500	[thread overview]
Message-ID: <4AAA8F61.9080905@freescale.com> (raw)
In-Reply-To: <7ee95fff0909111050m54f7ebdbq96f023263c09724f@mail.gmail.com>

Ken MacLeod wrote:
> On Fri, Sep 11, 2009 at 11:30 AM, Jerry Van Baren 
> <gerald.vanbaren at ge.com <mailto:gerald.vanbaren@ge.com>> wrote:
> 
>     Scott Wood wrote:
>      > On Thu, Sep 10, 2009 at 08:23:27PM -0400, Jerry Van Baren wrote:
>      >>    fdt set /ethernet at f00 interrupts "this is a string"
>      >> can now handle multiple strings (words) by concatenating them with
>      >> spaces (quoted strings still work the same as before because of
>     hush's
>      >> argument parsing)
>      >>    fdt set /ethernet at f00 interrupts this is a string
>      >
>      > How do you set a string list, then?
> 
> 
> The original code did not support string lists and this patch does not 
> address string lists.

This patch takes the most obvious syntax for supporting a string list in the 
future, and makes it mean something else.

-Scott

  reply	other threads:[~2009-09-11 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10 21:41 [U-Boot] [PATCH] cmd_fdt.c: fix parse of byte streams and strings Ken MacLeod
2009-09-11  0:23 ` Jerry Van Baren
2009-09-11 16:16   ` Scott Wood
2009-09-11 16:30     ` Jerry Van Baren
2009-09-11 16:39       ` Scott Wood
2009-09-11 16:45         ` Andy Fleming
2009-09-11 16:51           ` Jerry Van Baren
2009-09-11 17:50       ` Ken MacLeod
2009-09-11 17:56         ` Scott Wood [this message]
2009-09-11 19:35         ` Jerry Van Baren

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=4AAA8F61.9080905@freescale.com \
    --to=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.