From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Russell King <rmk@arm.linux.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Config files that aren't mach_defconfig...
Date: Tue, 30 Nov 2004 20:27:44 +0100 [thread overview]
Message-ID: <20041130192744.GA8777@mars.ravnborg.org> (raw)
In-Reply-To: <16811.41030.901140.963491@wombat.chubb.wattle.id.au>
On Tue, Nov 30, 2004 at 09:18:46AM +1100, Peter Chubb wrote:
>
> Hi Sam,
> I've just finished porting Linux 2.6 to a new ARM board, that needs
> a custom initramfs list. My approach was to set
> CONFIG_INITRAMFS_SOURCE to point to
> "$(srctree)/arch/arm/configs/pleb2_initramfs" in the appropriate
> defconfig for the board, as it's a default configuration item; but
> Russell asks if there isn't a better place for a per-board default initramfs
> script to live?
We have arch/$arch/configs for this specific purpose to store baord specific
configuration. So mixing *_defconfig and _initramfs is a natural choice.
Nothing is gained by introducing another directory for this purpose.
Sam
prev parent reply other threads:[~2004-11-30 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 22:18 Config files that aren't mach_defconfig Peter Chubb
2004-11-30 19:27 ` Sam Ravnborg [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=20041130192744.GA8777@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=rmk@arm.linux.co.uk \
/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.