From: Josh Boyer <jwboyer@gmail.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, sr@denx.de
Subject: Re: [PATCH] powerpc: add of_find_next_property and of_get_aliased_index
Date: Wed, 25 Jun 2008 19:51:49 -0400 [thread overview]
Message-ID: <1214437909.14225.122.camel@weaponx> (raw)
In-Reply-To: <1214424332-18496-1-git-send-email-timur@freescale.com>
On Wed, 2008-06-25 at 15:05 -0500, Timur Tabi wrote:
> +/**
> + * Return the first or next property within a node.
> + * @np: the node
> + * @prev: if NULL, return 1st prop, otherwise return the prop after 'prev'
> + *
> + * This function is used to get a list of properties within a node. It's
> + * also useful for when you don't know the name of the propety you want to
> + * find.
How is this useful when you don't know the name of the property you want
to find? I don't understand that at all.
I'm not really sure what good having a list of the properties within a
node is either, outside of using it for debugging.
josh
next prev parent reply other threads:[~2008-06-25 23:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 20:05 [PATCH] powerpc: add of_find_next_property and of_get_aliased_index Timur Tabi
2008-06-25 20:22 ` Segher Boessenkool
2008-06-25 20:27 ` Timur Tabi
2008-06-25 23:35 ` Segher Boessenkool
2008-06-26 15:12 ` Timur Tabi
2008-06-26 15:51 ` Stefan Roese
2008-06-26 15:55 ` Timur Tabi
2008-06-26 18:27 ` [PATCH] powerpc: add of_find_next_property andof_get_aliased_index Sean MacLennan
2008-06-26 18:29 ` Timur Tabi
2008-06-26 18:41 ` Stefan Roese
2008-06-27 1:30 ` David Gibson
2008-07-03 13:33 ` Josh Boyer
2008-07-03 13:43 ` Stefan Roese
2008-06-25 23:51 ` Josh Boyer [this message]
2008-06-26 10:57 ` [PATCH] powerpc: add of_find_next_property and of_get_aliased_index Benjamin Herrenschmidt
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=1214437909.14225.122.camel@weaponx \
--to=jwboyer@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
--cc=timur@freescale.com \
/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.