All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Matt Porter <mporter@embeddedalley.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Start arch/powerpc/boot code reorganization
Date: Sat, 23 Sep 2006 00:43:39 +0400	[thread overview]
Message-ID: <45144AFB.7030309@ru.mvista.com> (raw)
In-Reply-To: <20060922204013.GA29524@mag.az.mvista.com>

Hello.

Mark A. Greer wrote:

>>>3) The number of cells in the "size" portion of the tuple is indicated
>>>by the nearest #size-cells as you go up the tree.  Just like the "reg"
>>>property.

>>   Well, is there need for duplication of size if "reg" prop must be 
>>   present anyway?

> We're not adding another #size-cells, we're using the same one that
> "reg" uses.  No duplication, just reuse.

    I mean size could have been gotten from "reg" prop.

> Mark

WBR, Sergei

  reply	other threads:[~2006-09-22 20:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 23:00 [PATCH] Start arch/powerpc/boot code reorganization Paul Mackerras
2006-09-20  1:20 ` Mark A. Greer
2006-09-20  1:28   ` Mark A. Greer
2006-09-20 20:58     ` Mark A. Greer
2006-09-20  3:10   ` Josh Boyer
2006-09-20 20:23     ` Segher Boessenkool
2006-09-20 21:04       ` Josh Boyer
2006-09-20 21:32       ` Benjamin Herrenschmidt
2006-09-20 21:57         ` Mark A. Greer
2006-09-21  0:07           ` Segher Boessenkool
2006-09-21 13:37             ` Matt Porter
2006-09-21 14:15               ` Jon Loeliger
2006-09-21 14:26                 ` Matt Porter
2006-09-21 15:31               ` Segher Boessenkool
2006-09-22  1:24                 ` Mark A. Greer
2006-09-22  8:43                   ` Segher Boessenkool
2006-09-22 18:59                     ` Mark A. Greer
2006-09-22 19:36                       ` Sergei Shtylyov
2006-09-22 20:40                         ` Mark A. Greer
2006-09-22 20:43                           ` Sergei Shtylyov [this message]
2006-09-22 20:52                             ` Mark A. Greer
2006-09-22 20:56                               ` Sergei Shtylyov
2006-09-23  0:57                         ` Segher Boessenkool
2006-09-23 15:48                           ` Sergei Shtylyov
2006-09-23  0:54                       ` Segher Boessenkool
2006-09-23  8:18                         ` Mark A. Greer
2006-09-23 10:15                           ` Segher Boessenkool
2006-09-25 17:53                             ` Mark A. Greer
2006-09-25 23:40                               ` Segher Boessenkool
2006-09-25 23:44                                 ` Segher Boessenkool
2006-09-25 23:46                                 ` Mark A. Greer
2006-09-28 20:53                             ` Sergei Shtylyov
2006-09-30  8:36                               ` Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2006-09-19  3:21 Paul Mackerras
2006-09-19  4:22 ` Michael Ellerman
2006-09-19  4:29   ` Paul Mackerras

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=45144AFB.7030309@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.com \
    --cc=mporter@embeddedalley.com \
    --cc=paulus@samba.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 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.