From: blaisorblade_spam@yahoo.it
To: akpm@osdl.org
Cc: jdike@addtoit.com, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
blaisorblade_spam@yahoo.it, zippel@linux-m68k.org
Subject: [patch 1/1] uml: mark broken configs (fixed-up)
Date: Wed, 13 Oct 2004 19:20:40 +0200 [thread overview]
Message-ID: <20041013172041.2C3C58685@zion.localdomain> (raw)
From: Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it>, Roman Zippel <zippel@linux-m68k.org>
Some configuration options are known not to compile. So then make them
depend on CONFIG_BROKEN.
In this version, which completely replaces the previous one, posted yesterday
as "uml: mark broken configs", I do this:
menu "SCSI support"
+depends on BROKEN
instead of this:
-menu "SCSI support"
+if BROKEN
+ menu "SCSI support"
...
+endif
as was requested by Roman Zippel.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it>
---
linux-2.6.9-current-paolo/arch/um/Kconfig | 7 +++++--
linux-2.6.9-current-paolo/arch/um/Kconfig_block | 1 +
linux-2.6.9-current-paolo/arch/um/Kconfig_net | 2 +-
3 files changed, 7 insertions(+), 3 deletions(-)
diff -puN arch/um/Kconfig~uml-mark_broken_configs arch/um/Kconfig
--- linux-2.6.9-current/arch/um/Kconfig~uml-mark_broken_configs 2004-10-13 17:23:55.000000000 +0200
+++ linux-2.6.9-current-paolo/arch/um/Kconfig 2004-10-13 17:26:54.967233056 +0200
@@ -143,7 +143,6 @@ config SMP
will appear to be running simultaneously. If the host is a
multiprocessor, then UML processes may run simultaneously, depending
on the host scheduler.
- CONFIG_SMP will be set to whatever this option is set to.
It is safe to leave this unchanged.
config NR_CPUS
@@ -179,6 +178,7 @@ config KERNEL_HALF_GIGS
config HIGHMEM
bool "Highmem support"
+ depends on BROKEN
config KERNEL_STACK_ORDER
int "Kernel stack size order"
@@ -226,6 +226,7 @@ source "crypto/Kconfig"
source "lib/Kconfig"
menu "SCSI support"
+depends on BROKEN
config SCSI
tristate "SCSI support"
@@ -242,6 +243,8 @@ endmenu
source "drivers/md/Kconfig"
-source "drivers/mtd/Kconfig"
+if BROKEN
+ source "drivers/mtd/Kconfig"
+endif
source "arch/um/Kconfig.debug"
diff -puN arch/um/Kconfig_block~uml-mark_broken_configs arch/um/Kconfig_block
--- linux-2.6.9-current/arch/um/Kconfig_block~uml-mark_broken_configs 2004-10-13 17:23:55.000000000 +0200
+++ linux-2.6.9-current-paolo/arch/um/Kconfig_block 2004-10-13 17:23:55.920452304 +0200
@@ -54,6 +54,7 @@ config BLK_DEV_INITRD
config MMAPPER
tristate "Example IO memory driver"
+ depends on BROKEN
help
The User-Mode Linux port can provide support for IO Memory
emulation with this option. This allows a host file to be
diff -puN arch/um/Kconfig_net~uml-mark_broken_configs arch/um/Kconfig_net
--- linux-2.6.9-current/arch/um/Kconfig_net~uml-mark_broken_configs 2004-10-13 17:23:55.000000000 +0200
+++ linux-2.6.9-current-paolo/arch/um/Kconfig_net 2004-10-13 17:23:55.920452304 +0200
@@ -135,7 +135,7 @@ config UML_NET_MCAST
config UML_NET_PCAP
bool "pcap transport"
- depends on UML_NET
+ depends on UML_NET && BROKEN
help
The pcap transport makes a pcap packet stream on the host look
like an ethernet device inside UML. This is useful for making
_
reply other threads:[~2004-10-13 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041013172041.2C3C58685@zion.localdomain \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=zippel@linux-m68k.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®