From: Paul Kocialkowski <contact@paulk.fr>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Michal Marek <mmarek@suse.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [PATCH] kconfig: Add localdefconfig helper
Date: Sat, 26 Mar 2016 20:04:20 +0100 [thread overview]
Message-ID: <1459019060.971.3.camel@paulk.fr> (raw)
In-Reply-To: <20160326185306.GA4133@ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Le samedi 26 mars 2016 à 19:53 +0100, Sam Ravnborg a écrit :
> On Sat, Mar 26, 2016 at 07:31:27PM +0100, Paul Kocialkowski wrote:
> >
> > This introduces a localdefconfig make target to specify out-of-tree default
> > configs. The out-of-tree default target is selected by defining
> > KBUILD_LOCALDEFCONFIG in the make command line.
> >
> > The intent of this change is to easily allow using default configs that are
> > not
> > part of the kernel source (e.g. for a specific device or use case), without
> > ever
> > touching the kernel source tree.
> >
> Does this differ from what you can achieve with KCONFIG_ALLCONFIG?
> See Documentation/kbuild/kconfig.txt
>
> From a quick glance the functionality is the same.
It looks like my suggestion is equivalent to specifying KCONFIG_ALLCONFIG and
running the alldefconfig target, indeed!
Thanks for pointing this out, I suppose this patch can be disregarded then.
Cheers,
--
Paul Kocialkowski, low-level free software developer on embedded devices
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-26 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 18:31 [PATCH] kconfig: Add localdefconfig helper Paul Kocialkowski
2016-03-26 18:53 ` Sam Ravnborg
2016-03-26 19:04 ` Paul Kocialkowski [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=1459019060.971.3.camel@paulk.fr \
--to=contact@paulk.fr \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=sam@ravnborg.org \
--cc=yann.morin.1998@free.fr \
/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