From: "Josh Boyer" <jwboyer@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "David Woodhouse" <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MTD] Fix CFI build error with meaningless nonfunctional .config
Date: Sun, 12 Aug 2007 12:29:22 -0500 [thread overview]
Message-ID: <625fc13d0708121029k13b180c7i9abacbdf4a0647f8@mail.gmail.com> (raw)
In-Reply-To: <20070812162417.GA15412@elte.hu>
On 8/12/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> * David Woodhouse <dwmw2@infradead.org> wrote:
>
> > On Fri, 2007-08-10 at 09:41 +0200, Ingo Molnar wrote:
> > > looks quite quirky. Is there no Kconfig-space solution for this?
> >
> > I thought about that, but decided against it. We have altogether too
> > much munging of config options without the user's knowledge already; I
> > didn't want to make it worse.
>
> just found another one via randconfig, it fails with:
>
> In file included from drivers/mtd/chips/map_rom.c:16:
> include/linux/mtd/map.h:128:2: error: #error "No bus width supported. What's the point?"
>
> config attached below. Because it's so nice to be able to keep a
> randconfig build-test running overnight, i think this needs to be fixed
> too. (even if with just a runtime BUG())
Urgh. Is there a way to tell Kconfig, "One or more of the below
options must be set if CONFIG_CFI_GEOMETRY is enabled?"
josh
next prev parent reply other threads:[~2007-08-12 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 16:15 [build error] error: implicit declaration of function 'cfi_interleave' Ingo Molnar
2007-08-10 3:50 ` [PATCH] [MTD] Fix CFI build error with meaningless nonfunctional .config David Woodhouse
2007-08-10 7:41 ` Ingo Molnar
2007-08-10 7:45 ` David Woodhouse
2007-08-12 16:24 ` Ingo Molnar
2007-08-12 17:29 ` Josh Boyer [this message]
2007-08-13 0:00 ` David Woodhouse
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=625fc13d0708121029k13b180c7i9abacbdf4a0647f8@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®