linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 15/19] bootwrapper: Add dt_ops methods.
Date: Wed, 14 Mar 2007 15:33:24 +1100	[thread overview]
Message-ID: <17911.31508.878043.41229@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20070312204201.GO28545@ld0162-tx32.am.freescale.net>

Scott Wood writes:

> +static inline void *find_node_by_prop_value_str(const void *prev,
> +                                                const char *propname,
> +                                                const char *propval)

That name sure is a mouthful.  Since we mostly (only?) use it with
propname == "device_type", why not make a helper with a nice,
(relatively) short name like "find_node_by_type" for that case?

Paul.

  parent reply	other threads:[~2007-03-14  4:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 20:42 [PATCH 15/19] bootwrapper: Add dt_ops methods Scott Wood
2007-03-12 22:49 ` Mark A. Greer
2007-03-13 15:29   ` Scott Wood
2007-03-14  4:33 ` Paul Mackerras [this message]
2007-03-14 16:02   ` Scott Wood

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=17911.31508.878043.41229@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@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 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).