From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: arm allmodconfig
Date: Thu, 9 Aug 2007 01:03:16 +0200 [thread overview]
Message-ID: <200708090103.16295.mb@bu3sch.de> (raw)
In-Reply-To: <20070808155231.77bfc676.akpm@linux-foundation.org>
On Thursday 09 August 2007 00:52:31 Andrew Morton wrote:
> > Ok, I have no problem with that. BUT my users and other people
> > in the kernel community do certainly have. Nobody will find
> > the bcm43xx option anymore, if we depend on SSB.
> > I mean, people do even seriously complain about the filenames
> > of the firmware and so on.
> > So adding a dep on SSB would generate about 3 to 4
> > bugreports each day, I'd say from experience.
>
> yup, I understand the problem and I cannot suggest any acceptable solution,
> apart from...
>
> > So, once you suggested that menuconfig should be changed to
> > show options "greyed out" when deps are not met. Are there
> > any patches available? Any starting point?
>
> No, nothing at all, sorry.
>
> I'm getting a _lot_ of build breakage out of SSB right now.
Ok, I will do some patch that converts all this to dependencies
and I will later look for a solution to the other problem
created by this.
--
Greetings Michael.
next prev parent reply other threads:[~2007-08-08 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 21:57 arm allmodconfig Andrew Morton
2007-08-08 22:10 ` Ivo van Doorn
2007-08-08 22:13 ` Michael Buesch
2007-08-08 22:26 ` Andrew Morton
2007-08-08 22:32 ` Andrew Morton
2007-08-08 22:37 ` Andrew Morton
2007-08-08 22:38 ` Michael Buesch
2007-08-08 22:52 ` Andrew Morton
2007-08-08 23:03 ` Michael Buesch [this message]
2007-08-09 0:04 ` Michael Buesch
2007-08-09 0:21 ` Andrew Morton
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=200708090103.16295.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@vger.kernel.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).