linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig
Date: Fri, 16 Jul 2010 11:57:55 -0600	[thread overview]
Message-ID: <AANLkTinyFBTKYaryFANYheTuP-biJUws2x01NRNZPb4M@mail.gmail.com> (raw)
In-Reply-To: <1279296221.17878.66.camel@e102109-lin.cambridge.arm.com>

On Fri, Jul 16, 2010 at 10:03 AM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Wed, 2010-07-14 at 00:04 +0100, Grant Likely wrote:
>> - It still doesn't resolve dependencies. ?A solver would help with this.
>> ? For the time being I work around the problem by running the generated
>> ? config through 'oldconfig' and looking for differences. ?If the files
>> ? differ (ignoring comments and generateconfig_* options) after oldconfig,
>> ? then the <board>_defconfig target returns a failure. ?(but leaves the
>> ? new .config intact so the user can resolve it with menuconfig). ?This
>> ? way at least the user is told when a Kconfig fragment is invalid.
>
> It's not a solver but I'm pushing a patch to warn on selecting symbols
> with unmet dependencies so that you can select further symbols (manual
> solving). The patch is in linux-next but you also can grab it from:
>
> http://git.kernel.org/?p=linux/kernel/git/cmarinas/linux-2.6-cm.git;a=commitdiff_plain;h=5d87db2d2a332784bbf2b1ec3e141486f4d41d6f

sfr and I were talking about your patch the other day.  Just warning
on incomplete dependencies is enough to make it actually workable for
me (without my ugly post-processing step).  I was very happy to hear
that it is in linux-next.

Last missing piece is being able to do "select FOO = n", which Stephen
is currently working on.

g.

  reply	other threads:[~2010-07-16 17:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 23:04 [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig Grant Likely
2010-07-13 23:11 ` Grant Likely
2010-07-13 23:14 ` Daniel Walker
2010-07-13 23:21   ` Grant Likely
2010-07-13 23:33     ` Daniel Walker
2010-07-14  0:07       ` Nicolas Pitre
2010-07-14 16:22         ` Daniel Walker
2010-07-16 23:49           ` Jamie Lokier
2010-07-19  5:20             ` Grant Likely
2010-07-16 16:03 ` Catalin Marinas
2010-07-16 17:57   ` Grant Likely [this message]
2010-07-16 18:07     ` Russell King - ARM Linux
2010-07-16 18:17       ` Linus Torvalds
2010-07-16 18:18       ` Grant Likely
2010-07-16 18:19     ` Nicolas Pitre
2010-07-16 18:21       ` Grant Likely
2010-07-16 18:31         ` Nicolas Pitre
2010-07-16 18:30       ` Russell King - ARM Linux
2010-07-16 18:40         ` Nicolas Pitre
2010-07-16 18:46           ` Linus Torvalds
2010-07-16 20:09             ` Catalin Marinas
2010-07-16 20:17               ` Grant Likely
2010-07-16 20:29                 ` Nicolas Pitre
2010-07-16 20:37                   ` Grant Likely
2010-07-16 20:44                 ` Catalin Marinas
2010-07-16 20:11             ` Arnd Bergmann
2010-07-16 18:52         ` Grant Likely
2010-07-16 20:01     ` Arnd Bergmann

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=AANLkTinyFBTKYaryFANYheTuP-biJUws2x01NRNZPb4M@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).