From: Paul Mundt <lethal@linux-sh.org>
To: snogglethorpe@gmail.com, miles@gnu.org
Cc: Jan Dittmer <jdittmer@ppp0.net>, linux-kernel@vger.kernel.org
Subject: Re: defconfig for v850, please
Date: Wed, 20 Jul 2005 14:52:18 +0300 [thread overview]
Message-ID: <20050720115218.GB9754@linux-sh.org> (raw)
In-Reply-To: <fc339e4a0507200302d9f0141@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Wed, Jul 20, 2005 at 07:02:53PM +0900, Miles Bader wrote:
> Some archs seem to provide defconfigs for various different platforms,
> which seems nice, and there seems to be some sort of framework for
> doing this, but ...
>
For most of the architectures aimed at embedded systems, having an
arch/foo/defconfig makes no sense. The basic "framework" is to have
arch/foo/configs and place all of your board-specific defconfigs in there
(as boardname_defconfig -- the reason for this is that you get free make
targets of the same name which copy the defconfig over, see 'make help').
If you have a particular board that you can assume will be kept
reasonably up-to-date, you can set KBUILD_DEFCONFIG in your Makefile to
set the default config to use by name, and then you can forego having an
arch/foo/defconfig entirely (you can look at sh and some of the other
architectures to see this being done).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-20 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 9:22 defconfig for v850, please Jan Dittmer
2005-07-20 9:35 ` Miles Bader
2005-07-20 9:48 ` Jan Dittmer
2005-07-20 10:02 ` Miles Bader
2005-07-20 10:11 ` Jan Dittmer
2005-07-20 11:52 ` Paul Mundt [this message]
2005-07-20 13:01 ` Jan Dittmer
2005-07-20 14:20 ` Paul Mundt
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=20050720115218.GB9754@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=jdittmer@ppp0.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.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