linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@embeddedalley.com>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Start arch/powerpc/boot code reorganization
Date: Thu, 21 Sep 2006 10:26:53 -0400	[thread overview]
Message-ID: <20060921142653.GA20971@matthew-porters-computer.local> (raw)
In-Reply-To: <E1GQPKk-0003y1-Uq@jdl.com>

On Thu, Sep 21, 2006 at 09:15:22AM -0500, Jon Loeliger wrote:
> So, like, the other day Matt Porter mumbled:
> > 
> > Since the address prop sounds
> > like it will confuse some people I think it makes sense to add a
> > new property (might as well just throw out the spec :P).
> 
> Ayyyy, mate.  She be not so much a "code" as she be a "guideline".
 
Yeah, yeah, of course. We only use it when convenient.

> Huh?  That was the other day?  Neeeveeer mind.

:)

-Matt

  reply	other threads:[~2006-09-21 14:27 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 [this message]
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
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=20060921142653.GA20971@matthew-porters-computer.local \
    --to=mporter@embeddedalley.com \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --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 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).