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: Stefan@ozlabs.org, Roese <sr@denx.de>,
	Grant Erickson <gerickson@nuovations.com>,
	"linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] 4xx: Clone haleakala_defconfig from kilauea_defconfig
Date: Tue, 29 Jan 2008 16:22:52 -0700	[thread overview]
Message-ID: <fa686aa40801291522y49c1b7e7n83c035f80fef1a12@mail.gmail.com> (raw)
In-Reply-To: <20080129165941.1681842f@zod.rchland.ibm.com>

On 1/29/08, Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> On Tue, 29 Jan 2008 14:49:59 -0800
> Grant Erickson <gerickson@nuovations.com> wrote:
>
> > On 1/29/08 2:09 PM, Josh Boyer wrote:
> > > On Tue, 29 Jan 2008 14:05:41 -0800
> > > Grant Erickson <gerickson@nuovations.com> wrote:
> > >
> > >> Is there a patch pending to for 'arch/powerpc/configs/haleakala_defconfig'?
> > >
> > > Not to my knowledge.
> > >
> > >> I did not see one in either of:
> > >>
> > >>     git://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git
> > >>     git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
> > >>
> > >> If no patch is pending, to whom do I submit such a patch? It'll simply be a
> > >> near clone of 'kilauea_defconfig', save the "CONFIG_DEVICE_TREE" entry.
> > >
> > > Send one to me.  CC Stefan Roese please.
> > >
> > > josh
> >
> > * Allow for 'make haleakala_defconfig' by providing a default configuration
> >   for the AMCC PowerPC 405EXr "Haleakala" board.
> >
>
> As silly as it sounds, I need a Signed-off-by for this.  Could you read
> Documentation/SubmittingPatches section 12 and just reply to this with
> a Signed-off-by line?

Rather than adding more defconfigs, can we have a single defconfig for
440 and another one for 405?  The configs directory is getting a bit
silly.

I've consolidated the defconfigs for 5200 and Kumar is doing the same
for 8xxx.  All the pasemi platforms have used a single defconfig for a
while now.

Cheers,
g.

>
> josh
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>


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

  parent reply	other threads:[~2008-01-29 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 22:05 Haleakala Defconfg Grant Erickson
2008-01-29 22:09 ` Josh Boyer
2008-01-29 22:49   ` [PATCH] 4xx: Clone haleakala_defconfig from kilauea_defconfig Grant Erickson
2008-01-29 22:59     ` Josh Boyer
2008-01-29 23:10       ` Grant Erickson
2008-01-29 23:22       ` Grant Likely [this message]
2008-01-30  0:07         ` Josh Boyer
2008-01-30  0:12           ` Grant Likely
2008-01-30  0:40             ` Josh Boyer
2008-01-30  6:22               ` Stefan Roese

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=fa686aa40801291522y49c1b7e7n83c035f80fef1a12@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Stefan@ozlabs.org \
    --cc=gerickson@nuovations.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sr@denx.de \
    /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).