From: Grant Likely <grant.likely@secretlab.ca>
To: Niklaus Giger <niklaus.giger@member.fsf.org>
Cc: linuxppc-dev@ozlabs.org, niklaus.giger@netstal.com
Subject: Re: [PATCH 1/1] powerpc/40x: Add new PPC440EPx based board HCU5 of Netstal Maschinen
Date: Sun, 1 Nov 2009 01:12:42 -0600 [thread overview]
Message-ID: <fa686aa40911010012g66f46950n4330e9d564b7c420@mail.gmail.com> (raw)
In-Reply-To: <1255075865-4025-2-git-send-email-niklaus.giger@member.fsf.org>
On Fri, Oct 9, 2009 at 2:11 AM, Niklaus Giger
<niklaus.giger@member.fsf.org> wrote:
> Adds support for a HCU5 PPC405EPx based board from Netstal Maschinen AG.
>
> Signed-off-by: Niklaus Giger <niklaus.giger@member.fsf.org>
> ---
> =A0arch/powerpc/boot/dts/hcu5.dts =A0 =A0 =A0 =A0 =A0| =A0254 +++++++
> =A0arch/powerpc/configs/44x/hcu5_defconfig | 1166 +++++++++++++++++++++++=
++++++++
Do you really need your own defconfig? Can you instead add support
for your board to ppc44x_defconfig? Josh is the maintainer here, so
it is his decision, but on 5200 stuff I've been pushing back on adding
yet-another-board-specific-defconfig when there isn't a really
compelling reason to do so. It adds a lot of lines for not a lot of
benefit. Besides, if you add your board to the ppc44x_defconfig, you
gain the advantage of your code getting compiled by others more
frequently.
g.
prev parent reply other threads:[~2009-11-01 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 8:11 [PATCH 0/1] powerpc/40x: Add new PPC440EPx based board HCU5 of Netstal Maschinen Niklaus Giger
2009-10-09 8:11 ` [PATCH 1/1] " Niklaus Giger
2009-10-12 12:32 ` Josh Boyer
2009-11-01 7:12 ` Grant Likely [this message]
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=fa686aa40911010012g66f46950n4330e9d564b7c420@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=niklaus.giger@member.fsf.org \
--cc=niklaus.giger@netstal.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 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).