From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org
Subject: Re: libfdt: Fix bugs in fdt_get_path()
Date: Thu, 25 Sep 2008 10:01:27 -0500 [thread overview]
Message-ID: <E1KisLP-0007uK-Vf@jdl.com> (raw)
In-Reply-To: <20080829041913.GC30197@yookeroo.seuss>
> The current implementation of fdt_get_path() has a couple of bugs,
> fixed by this patch.
>
> First, contrary to its documentation, on success it returns the length
> of the node's path, rather than 0. The testcase is correspondingly
> wrong, and the patch fixes this as well.
>
> Second, in some circumstances, it will return -FDT_ERR_BADOFFSET
> instead of -FDT_ERR_NOSPACE when given insufficient buffer space.
> Specifically this happens when there is insufficient space even to
> hold the path's second last component. This behaviour is corrected,
> and the testcase updated to check it.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied.
Thanks,
jdl
prev parent reply other threads:[~2008-09-25 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 4:19 libfdt: Fix bugs in fdt_get_path() David Gibson
2008-09-25 15:01 ` 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=E1KisLP-0007uK-Vf@jdl.com \
--to=jdl@jdl.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).