The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cloning arch-independant KConfig
Date: Thu, 12 Aug 2010 18:30:59 -0700	[thread overview]
Message-ID: <20100813013059.GJ22777@mail.oracle.com> (raw)
In-Reply-To: <20100813012052.GA2079@merkur.ravnborg.org>

On Fri, Aug 13, 2010 at 03:20:52AM +0200, Sam Ravnborg wrote:
> Today there are a few ways you can do so already.
> Say that you have saved away the known good one as "good", which is
> a direct copy of your .config.
> 
> Then you can do for example:
> KCONFIG_ALLCONFIG=good make alldefconfig
> 
> This will produce a config wich is almost equal to what you had before,
> and with defaults for all new stuff.
> I tested it where I used a sparc defconfig as input to a i386
> config and it just worked.

	That seems pretty reasonable.

> cat .config good > new
> mv new .config
> make menuconfig
> 
> This will trigger a lot of override warnings - which you just ignore.
> Resulting config is then mostly from "good".

	The problem with this, which I've definitely done before, is I
never know what paths in menuconfig to look down.  The alldefconfig
choice seems saner because it provides a dirt-simple CPU setup.

Joel

-- 

"Can any of you seriously say the Bill of Rights could get through
 Congress today?  It wouldn't even get out of committee."
	- F. Lee Bailey

Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

      reply	other threads:[~2010-08-13  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 23:38 Cloning arch-independant KConfig Joel Becker
2010-08-13  1:20 ` Sam Ravnborg
2010-08-13  1:30   ` Joel Becker [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=20100813013059.GJ22777@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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