linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, jdl@jdl.com
Subject: Re: [DTC PATCH] libfdt: Add ft_get_next_node(), ft_get_next_prop(), and ft_getprop_offset().
Date: Mon, 14 Jan 2008 16:44:33 -0600	[thread overview]
Message-ID: <478BE5D1.9080300@freescale.com> (raw)
In-Reply-To: <20080115093149.39a1d703.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
>> +++ b/libfdt/libfdt.h
> 
>> +#define FDT_ERR_BADDEPTH	8
> 
> Wouldn't it have been less intrusive to just use the next error number
> rather than inserting this here?

Yes, but then either the order in errtable[] wouldn't match the order in 
the header file, or the error type grouping would be broken.

If we want to maintain such a grouping, we should probably leave some 
number space between the groups.

>> + * fdt_getprop_offset - retrieve the value of a given property by offset
>> + * @fdt: pointer to the device tree blob
>> + * @propoffset: offset of the property to read
>> + * @name: pointer to a character pointer (will be overwritten) or NULL
>                           ^^^^^^^^^^^^^^^^^
> "string"?

"pointer to a string" could be interpreted as "char *", not "char **".

I'll fix the others; thanks for pointing them out.

-Scott

  reply	other threads:[~2008-01-14 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 16:30 [DTC PATCH] libfdt: Add ft_get_next_node(), ft_get_next_prop(), and ft_getprop_offset() Scott Wood
2008-01-14 22:31 ` Stephen Rothwell
2008-01-14 22:44   ` Scott Wood [this message]
2008-01-14 22:54     ` Stephen Rothwell
2008-01-15  0:16 ` David Gibson
2008-01-15 16:52   ` Scott Wood
2008-01-16  3:49     ` David Gibson
2008-01-16  7:15       ` David Gibson

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=478BE5D1.9080300@freescale.com \
    --to=scottwood@freescale.com \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).