linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>
Cc: Olof Johansson <olof@lixom.net>, linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull linux-2.6-mpc52xx.git
Date: Fri, 4 Apr 2008 11:25:00 -0600	[thread overview]
Message-ID: <fa686aa40804041025i552c64e6j87fcb743e398ddf9@mail.gmail.com> (raw)
In-Reply-To: <1207329303.6518.16.camel@weaponx>

On Fri, Apr 4, 2008 at 11:15 AM, Josh Boyer >  > I really like the
idea. It would probably make sense to organize it in
>  > the same way as the platforms are done today, i.e. per processor/platform
>  > family. And then have shared/merged configs in the main config directory.
>
>  Yes.  I was thinking the same already for 4xx.  Essentially:
>
>  configs/ppc44x_defconfig
>  configs/ppc40x_defconfig
>  configs/44x/<board>_defconfig
>  configs/40x/<board>_defconfig

Sounds logical.  I'm cool with this.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-04-04 17:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  7:35 Please pull linux-2.6-mpc52xx.git Grant Likely
     [not found] ` <47DE94F4.90804@semihalf.com>
2008-03-17 19:19   ` Grant Likely
2008-03-17 20:59     ` Wolfgang Denk
2008-03-17 21:43       ` Grant Likely
2008-03-17 22:28         ` Wolfgang Denk
2008-03-17 23:43           ` Grant Likely
2008-03-18  0:26             ` Wolfgang Denk
2008-03-18  2:42               ` Grant Likely
2008-03-18 12:20                 ` Josh Boyer
2008-03-18  8:29             ` Bartlomiej Sieka
2008-03-18 10:04               ` Richard Purdie
2008-03-25 15:29                 ` Bartlomiej Sieka
2008-03-18 14:47               ` Grant Likely
2008-03-18 16:41                 ` Richard Purdie
2008-03-18 16:53                   ` Grant Likely
2008-03-25 16:50                     ` Bartlomiej Sieka
2008-03-25 18:49                       ` Grant Likely
2008-03-25 17:38             ` Bartlomiej Sieka
2008-03-25 18:51               ` Grant Likely
2008-04-01 12:37                 ` Bartlomiej Sieka
2008-04-04 11:13                   ` Bartlomiej Sieka
2008-04-04 16:11                     ` Grant Likely
2008-04-04 16:14                       ` Grant Likely
2008-04-04 16:38                         ` Olof Johansson
2008-04-04 17:15                           ` Josh Boyer
2008-04-04 17:25                             ` Grant Likely [this message]
2008-04-15 10:34                       ` Bartlomiej Sieka
2008-03-18  7:57     ` Bartlomiej Sieka
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09 23:09 Grant Likely
2008-11-14 19:20 Grant Likely
2008-11-24  3:38 ` Paul Mackerras
2008-11-24 14:41   ` Grant Likely
2008-05-01 18:04 Grant Likely
2008-04-29 13:34 Grant Likely
2007-10-16 23:22 Grant Likely
2007-10-17 10:27 ` Paul Mackerras
2007-10-17 13:13   ` Grant Likely
2007-10-10 16:30 Grant Likely
2007-10-11 17:35 ` tnt

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=fa686aa40804041025i552c64e6j87fcb743e398ddf9@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).