LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: libfdt: Implement fdt_get_property_namelen() and fdt_getprop_namelen()
Date: Wed, 13 Aug 2008 13:09:44 -0500	[thread overview]
Message-ID: <E1KTKn2-0000Jn-Fu@jdl.com> (raw)
In-Reply-To: <20080806045049.GC6690@yookeroo.seuss>

> As well as fdt_subnode_offset(), libfdt includes an
> fdt_subnode_offset_namelen() function that takes the subnode name to
> look up not as a NUL-terminated string, but as a string with an
> explicit length.  This can be useful when the caller has the name as
> part of a longer string, such as a full path.
> 
> However, we don't have corresponding 'namelen' versions for
> fdt_get_property() and fdt_getprop().  There are less obvious use
> cases for these variants on property names, but there are
> circumstances where they can be useful e.g. looking up property names
> which need to be parsed from a longer string buffer such as user input
> or a configuration file, or looking up an alias in a path with
> IEEE1275 style aliases.
> 
> So, since it's very easy to implement such variants, this patch does
> so.  The original NUL-terminated variants are, of course, implemented
> in terms of the namelen versions.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

jdl

      reply	other threads:[~2008-08-13 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  4:50 libfdt: Implement fdt_get_property_namelen() and fdt_getprop_namelen() David Gibson
2008-08-13 18:09 ` Jon Loeliger [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=E1KTKn2-0000Jn-Fu@jdl.com \
    --to=jdl@jdl.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    /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