From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@osdl.org>, Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm1
Date: Tue, 22 Jun 2004 07:33:49 +0200 [thread overview]
Message-ID: <20040622053349.GA2738@mars.ravnborg.org> (raw)
In-Reply-To: <20040621020420.GL27822@fs.tum.de>
On Mon, Jun 21, 2004 at 04:04:20AM +0200, Adrian Bunk wrote:
> On Sun, Jun 20, 2004 at 05:46:32PM -0700, Andrew Morton wrote:
> >...
> > +wanxl-firmware-build-fix.patch
> >
> > Fix allmodconfig build
> >...
>
> This option is in drivers/base/Kconfig, but the similar option
> STANDALONE [1] is in init/Kconfig.
>
> Shouldn't buoth be at the same place?
> What about moving STANDALONE ad let it depend on PREVENT_FIRMWARE_BUILD?
STANDALONE avoids any drivers not using external firmware.
PREVENT_FIRMWARE_BUILD just prevents the supplied firmware to be build.
So no I do not see they should be dependent.
But for sure they should be located in the same place.
This is drivers only information and not related to the actual
maturity of the code - so moving STANDALONE to drivers/base
makes sense to me.
Adrian - care to submit a patch?
Sam
next prev parent reply other threads:[~2004-06-22 5:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 0:46 2.6.7-mm1 Andrew Morton
2004-06-21 1:40 ` 2.6.7-mm1: empty help text for FB_RIVA_I2C Adrian Bunk
2004-06-21 7:38 ` Antonino A. Daplas
2004-06-21 1:43 ` [patch] 2.6.7-mm1: R8169_NAPI help text Adrian Bunk
2004-06-21 1:55 ` [patch] 2.6.7-mm1: drivers/scsi/hosts.h -> scsi/scsi_host.h Adrian Bunk
2004-06-22 3:48 ` Jeff Garzik
2004-06-21 2:04 ` 2.6.7-mm1 Adrian Bunk
2004-06-22 5:33 ` Sam Ravnborg [this message]
2004-07-17 20:46 ` [2.6 patch] move STANDALONE to drivers/base/Kconfig Adrian Bunk
2004-06-21 2:06 ` 2.6.7-mm1 linker trouble with CONFIG_FB_RIVA_I2C=y and modular I2C Matthias Andree
2004-06-21 15:29 ` [patch] " Adrian Bunk
2004-06-22 15:11 ` Matthias Andree
2004-06-21 10:48 ` 2.6.7-mm1 Dominik Karall
2004-06-21 11:00 ` 2.6.7-mm1 Andrew Morton
2004-06-21 11:43 ` 2.6.7-mm1 Dominik Karall
2004-06-23 7:28 ` 2.6.7-mm1 Daniele Venzano
2004-06-21 11:48 ` 2.6.7-mm1 Eric BEGOT
2004-06-21 14:25 ` 2.6.7-mm1 James Morris
2004-06-21 14:38 ` 2.6.7-mm1 Eric BEGOT
2004-06-22 0:15 ` 2.6.7-mm1 Adrian Bunk
2004-06-21 14:32 ` 2.6.7-mm1 (compile stats) John Cherry
2004-06-21 23:05 ` 2.6.7-mm1 I/O regression ? FabF
2004-06-21 23:18 ` FabF
2004-06-21 19:57 2.6.7-mm1 Luca Risolia
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=20040622053349.GA2738@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®