From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] make xconfig broken in ia64-020622
Date: Thu, 11 Jul 2002 21:24:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905766@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905745@msgid-missing>
>>>>> On Wed, 10 Jul 2002 11:05:19 -0600, Khalid Aziz <khalid@fc.hp.com> said:
Khalid> Absolutely. xconfig parser has major problems with the
Khalid> following patch to arch/ia64/config.in in 020622:
Khalid> +else # ! HP_SIM
Khalid> +mainmenu_option next_comment
Khalid> +comment 'Block devices'
Khalid> +tristate 'Loopback device support' CONFIG_BLK_DEV_LOOP
Khalid> +dep_tristate 'Network block device support' CONFIG_BLK_DEV_NBD
Khalid> $CONFIG_NET
Khalid> +
Khalid> +tristate 'RAM disk support' CONFIG_BLK_DEV_RAM
Khalid> +if [ "$CONFIG_BLK_DEV_RAM" = "y" -o "$CONFIG_BLK_DEV_RAM" = "m" ]; then
Khalid> + int ' Default RAM disk size' CONFIG_BLK_DEV_RAM_SIZE 4096
Khalid> +fi
Khalid> +endmenu
Khalid> xconfig parser looks at this definition of 'Block devices'
Khalid> and the one in drivers/block/Config.in and considers them
Khalid> duplicates inspite of the conditional. With this patch, you
Khalid> can not configure loopback device or RAM disk unless you are
Khalid> configuring for HP Simulator.
Khalid> Without the patch I sent, "make xconfig" won't even
Khalid> start. So this patch only makes xconfig atleast partially
Khalid> usable.
If nobody wants to fix this problem, perhaps what we should do is
change "make xconfig" so it just prints a message telling the user to
do "make menuconfig" instead. Other suggestions (and particular patches)
are welcome...
--david
next prev parent reply other threads:[~2002-07-11 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 15:53 [Linux-ia64] [PATCH] make xconfig broken in ia64-020622 Khalid Aziz
2002-07-10 16:06 ` Xavier Bru
2002-07-10 17:05 ` Khalid Aziz
2002-07-11 21:24 ` David Mosberger [this message]
2002-07-12 20:46 ` Khalid Aziz
2002-07-19 6:54 ` Keith Owens
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=marc-linux-ia64-105590701905766@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.