From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: Thierry Escande <thierry.escande@linux.intel.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH v3 8/8] build: add NFC defconfig file
Date: Mon, 08 Apr 2013 21:40:36 +0200 [thread overview]
Message-ID: <1365450036.25475.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6X6+M2-eUeqTv-PAJDQ_VaLwUv3n94J1YTR+4CK7YYdaw@mail.gmail.com> (sfid-20130408_213755_513280_4A96F3C1)
On Mon, 2013-04-08 at 12:37 -0700, Luis R. Rodriguez wrote:
> >> > +CPTCFG_NFC=m
[...]
> >> Johannes, do we want to be disabling the other subsystems in these ?
> >
> > Well anything not listed will have the default values, so that should be
> > OK, right? Most things should be default off.
>
> OK so the default would be -- "if you have it on your kernel then
> we'll enable at build time", is that right? I wasn't clear on this,
> that's all.
No, because of the prefix rename (CONFIG_ -> CPTCFG_) the kernel's
configuration has no influence on our configuration at all.
So the default is just whatever the default is in the Kconfig files,
which is essentially everything else turned off.
johannes
next prev parent reply other threads:[~2013-04-08 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 10:26 [PATCH v3 8/8] build: add NFC defconfig file Thierry Escande
2013-04-08 19:31 ` Luis R. Rodriguez
2013-04-08 19:34 ` Johannes Berg
2013-04-08 19:37 ` Luis R. Rodriguez
2013-04-08 19:40 ` Johannes Berg [this message]
2013-04-08 20:51 ` Luis R. Rodriguez
2013-04-08 20:56 ` Johannes Berg
2013-04-08 20:57 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2013-04-05 21:20 Thierry Escande
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=1365450036.25475.21.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=thierry.escande@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.