From: Sam Ravnborg <sam@ravnborg.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Add ``cloneconfig'' target
Date: Sat, 26 Feb 2011 23:18:38 +0100 [thread overview]
Message-ID: <20110226221838.GA24028@merkur.ravnborg.org> (raw)
In-Reply-To: <AANLkTimFd+KFKgiOF8iVoM8Pk77Zy+5CsFs5BCYqCw=L@mail.gmail.com>
On Sat, Feb 26, 2011 at 02:47:01PM -0500, Arnaud Lacombe wrote:
> Hi,
>
> On Fri, Feb 25, 2011 at 1:07 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
> > We already have something remotely similar in kconfig.
> > We use the following list:
> > config DEFCONFIG_LIST
> > string
> > depends on !UML
> > option defconfig_list
> > default "/lib/modules/$UNAME_RELEASE/.config"
> > default "/etc/kernel-config"
> > default "/boot/config-$UNAME_RELEASE"
> > default "$ARCH_DEFCONFIG"
> > default "arch/$ARCH/defconfig"
> >
> I may argue that anything within the Linux tree which point
> _by_default_ to something outside the tree itself is broken.
The above allows the average user to just type "make menuconfig"
and then the configuration of the current kernel is presented to
the user. This is convinient in many cases.
We know the /proc/config.gz is an incresingly popular way to gain
access to the configuration of the running kernel. So extending
the already know and working way to obtaing the configuration
of the running kernel to suppport /proc/config.gz is logical.
The fact that the configuration is gzipped does not warrant
a new option to deal with this that almost duplicate the
existing functionality.
Sam
next prev parent reply other threads:[~2011-02-26 22:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 2:35 Jeff Mahoney
2011-02-25 6:07 ` Sam Ravnborg
2011-02-26 0:44 ` [PATCH 1/2] kconfig: add support for type handlers Jeff Mahoney
2011-02-26 1:28 ` Arnaud Lacombe
2011-02-26 17:27 ` Jeff Mahoney
2011-02-26 0:44 ` [PATCH 2/2] kconfig: Use /proc/config.gz as a configuration source Jeff Mahoney
2011-02-26 19:47 ` [PATCH] Add ``cloneconfig'' target Arnaud Lacombe
2011-02-26 22:18 ` Sam Ravnborg [this message]
2011-02-26 23:03 ` Arnaud Lacombe
2011-02-26 23:28 ` Arnaud Lacombe
2011-02-27 18:44 ` Sam Ravnborg
2011-02-27 9:03 ` Geert Uytterhoeven
2011-02-27 17:13 ` Arnaud Lacombe
2011-02-27 17:54 ` Jeff Mahoney
2011-02-26 22:47 ` Miguel Ojeda
2011-02-26 22:57 ` Arnaud Lacombe
2011-02-26 23:16 ` Miguel Ojeda
2011-02-26 23:26 ` Arnaud Lacombe
2011-02-26 23:38 ` Jeff Mahoney
2011-02-26 23:50 ` Arnaud Lacombe
2011-02-26 23:34 ` Jeff Mahoney
2011-02-26 23:53 ` Arnaud Lacombe
2011-02-26 19:50 ` Arnaud Lacombe
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=20110226221838.GA24028@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jeffm@suse.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®