From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: David Gibson <dwg-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: dtc: Return code of fdt_get_path()
Date: Tue, 05 Aug 2008 16:12:22 -0500 [thread overview]
Message-ID: <4898C236.5030305@freescale.com> (raw)
The documentation for fdt_get_path() says it returns zero on success,
but it actually returns the length of the string. Is there any
preference on which one to fix?
-Scott
next reply other threads:[~2008-08-05 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 21:12 Scott Wood [this message]
[not found] ` <4898C236.5030305-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-08-06 5:33 ` dtc: Return code of fdt_get_path() David Gibson
[not found] ` <20080806053310.GF6690-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-08-07 6:08 ` David Gibson
[not found] ` <20080807060820.GA12571-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-08-12 15:57 ` Jon Loeliger
2008-08-12 23:15 ` David Gibson
2008-08-29 3:07 ` 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=4898C236.5030305@freescale.com \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=dwg-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.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