All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milton Miller <miltonm@bga.com>
To: Scott Wood <scottwood@freescale.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 10/61] bootwrapper: flatdevtree fixes
Date: Thu, 19 Jul 2007 00:45:18 -0500	[thread overview]
Message-ID: <d385cb2ef0d915731d915efc3a8e6dff@bga.com> (raw)
In-Reply-To: <469E6241.5090604@freescale.com>

On Jul 18, 2007, at 1:56 PM, Scott Wood wrote:
> Milton Miller wrote:
>> In-Reply-To: <20070718013137.GA15217@ld0162-tx32.am.freescale.net>
>> On Wed Jul 18 11:33:08 EST 2007, Scott Wood wrote:
>>> 1. ft_create_node was returning the internal pointer rather than a 
>>> phandle.
>>> 2. ft_find_device_rel was treating lookups relative to root as an 
>>> error.
>> No, it is treating lookups relative to NULL as an error.
>> Your patch changes it to treat lookups relative to the NULL phandle 
>> as relative to root.
>
> Other parts of the code (such as ft_create_node) already do that. 
> What's wrong with it?

Well, that behavior may be ok, but the change log should say that is 
the behavior you are changing.

Ie I would record 2 as:

When ft_find_device_rel is asked to find relative to NULL, find 
realative to root instead of returning an error.

or:

ft_find_device_rel now treats lookups relative to NULL as relative to 
the root instead of erroring out.


My reading would say that lookups relative to the phandle of root would 
have workied before, no?

>
>> I've no objections to the other part, can you split these?
>
> No, because change #1 won't work without change #2.

Huh?

I can see how changing a routine to return an external not internal 
pointer is necessary before changing a caller creates a dependancy for 
2 on 1, but why does it require lookups relative to the phandle NULL be 
treated as lookups relative to the root?

milton

  reply	other threads:[~2007-07-19  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 15:43 [PATCH 10/61] bootwrapper: flatdevtree fixes Milton Miller
2007-07-18 18:56 ` Scott Wood
2007-07-19  5:45   ` Milton Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-18  1:31 [PATCH 01/61] Use strcasecmp() rather than strncasecmp() when determining device node compatibility Scott Wood
2007-07-18  1:33 ` [PATCH 10/61] bootwrapper: flatdevtree fixes Scott Wood
2007-07-18 16:20   ` Milton Miller

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=d385cb2ef0d915731d915efc3a8e6dff@bga.com \
    --to=miltonm@bga.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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.