public inbox for linuxppc-dev@ozlabs.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, devicetree-discuss@ozlabs•org
Subject: Re: libfdt: Fix bug in fdt_subnode_offset_namelen()
Date: Wed, 05 Nov 2008 08:15:38 -0600	[thread overview]
Message-ID: <E1KxjAZ-0006VP-0K@jdl.com> (raw)
In-Reply-To: <20081030024108.GC17505@yookeroo.seuss>

> There's currently an off-by-one bug in fdt_subnode_offset_namelen()
> which causes it to keep searching after it's finished the subnodes of
> the given parent, and into the subnodes of siblings of the original
> node which come after it in the tree.
> 
> This patch fixes the bug.  It also extends the subnode_offset testcase
> (updating all of the 'test_tree1' example trees in the process) to
> catch it.
> 
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>

Applied.

Thanks,
jdl

      reply	other threads:[~2008-11-05 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  2:41 libfdt: Fix bug in fdt_subnode_offset_namelen() David Gibson
2008-11-05 14:15 ` 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=E1KxjAZ-0006VP-0K@jdl.com \
    --to=jdl@jdl$(echo .)com \
    --cc=david@gibson$(echo .)dropbear.id.au \
    --cc=devicetree-discuss@ozlabs$(echo .)org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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