public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Jan Dittmer <jdittmer@ppp0.net>
Cc: snogglethorpe@gmail.com, miles@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: defconfig for v850, please
Date: Wed, 20 Jul 2005 17:20:08 +0300	[thread overview]
Message-ID: <20050720142008.GA6762@linux-sh.org> (raw)
In-Reply-To: <42DE4B44.80504@ppp0.net>

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

On Wed, Jul 20, 2005 at 03:01:56PM +0200, Jan Dittmer wrote:
> Still, for basic compile testing and testing patches on other
> architectures it would be nice, when the patch writer can test his/her
> patch with a simple defconfig, without knowing a common platform for
> this target arch.

This is what KBUILD_DEFCONFIG is for. A general purpose defconfig that
has no hope of being kept up-to-date is worse than useless.

> arm is another one which uses this style, ia64 for example uses configs/*
> and defconfig. But on arm and sh `make defconfig` works contrary to v850.
> 
That's because it looks at KBUILD_DEFCONFIG.. We absolutely do not want
to have an arch/foo/defconfig for most of these architectures, and I
doubt that v850 is an exception. Note that sh also does not have one.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-07-20 14:20 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
2005-07-20 13:01         ` Jan Dittmer
2005-07-20 14:20           ` Paul Mundt [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=20050720142008.GA6762@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