From: Keith Owens <kaos@ocs.com.au>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre3
Date: Tue, 12 Mar 2002 10:14:35 +1100 [thread overview]
Message-ID: <4656.1015888475@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 12 Mar 2002 10:04:42 +1100." <3C8D380A.166A7895@eyal.emu.id.au>
On Tue, 12 Mar 2002 10:04:42 +1100,
Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> dep_tristate ' Indy/I2 Hardware Watchdog' CONFIG_INDYDOG
>$CONFIG_SGI_IP22
>
>Looks OK to me though. However CONFIG_SGI_IP22 is not set anywhere,
>should
>dep_tristate treat it as FALSE?
That is a restriction on CML1, particularly when using any of the
config options that rely on shell scripts. CONFIG_SGI_IP22 is
undefined for i386 and the shell converts $CONFIG_SGI_IP22 to blank,
before CML1 even sees it. Doing dep_* on options that might be
undefined is unreliable. This works :-
if [ "$CONFIG_SGI_IP22" = "y" ]; then
tristate ' Indy/I2 Hardware Watchdog' CONFIG_INDYDOG
fi
next prev parent reply other threads:[~2002-03-11 23:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 21:08 Linux 2.4.19-pre3 Marcelo Tosatti
2002-03-11 22:40 ` Eyal Lebedinsky
2002-03-11 23:03 ` Alan Cox
2002-03-11 22:55 ` Stephan von Krawczynski
2002-03-12 1:50 ` Mike Fedyk
2002-03-12 11:06 ` Stephan von Krawczynski
2002-03-12 21:59 ` Paul Mackerras
2002-03-11 23:04 ` Eyal Lebedinsky
2002-03-11 23:14 ` Keith Owens [this message]
2002-03-12 15:49 ` DevilKin
2002-03-21 12:06 ` [patch] Don't offer CONFIG_INDYDOG on non-ip22 machines Adrian Bunk
2002-03-22 21:13 ` Marcelo Tosatti
2002-03-11 23:21 ` Linux 2.4.19-pre3 Eyal Lebedinsky
2002-03-12 1:40 ` Takeo Saito
2002-03-12 0:04 ` J.A. Magallon
2002-03-12 0:37 ` Ken Brownfield
2002-03-19 2:41 ` I/O APIC fixed in 2.4.19-pre3 & 2.5.6 (was Re: Linux 2.4.19-pre3) Ken Brownfield
2002-03-19 16:22 ` Bill Davidsen
2002-03-20 0:34 ` Ken Brownfield
2002-03-20 4:36 ` Bill Davidsen
2002-03-12 10:35 ` Linux 2.4.19-pre3 Gerd Knorr
2002-03-12 17:24 ` Trond Myklebust
2002-03-12 17:47 ` Gerd Knorr
2002-03-12 13:01 ` Karsten Weiss
2002-03-12 13:17 ` Jens Axboe
2002-03-12 13:37 ` Alan Cox
2002-03-12 13:46 ` Jens Axboe
2002-03-12 19:02 ` Marcelo Tosatti
2002-03-13 8:09 ` Jens Axboe
2002-03-13 9:00 ` Andre Hedrick
2002-03-13 9:27 ` Jens Axboe
2002-03-13 9:33 ` Andre Hedrick
2002-03-13 17:32 ` Andre Hedrick
2002-03-13 17:40 ` Jens Axboe
2002-03-13 18:52 ` Andre Hedrick
2002-03-14 4:41 ` Marcelo Tosatti
2002-03-14 6:28 ` Andre Hedrick
2002-03-14 3:32 ` Michal Jaegermann
2002-03-12 14:47 ` J.A. Magallon
2002-03-12 13:31 ` Jurgen Philippaerts
2002-03-12 15:43 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 0:51 Mikael Pettersson
2002-03-12 5:13 ` skidley
2002-03-12 21:00 ` Dave Jones
[not found] <fa.npg7nmv.si46bq@ifi.uio.no>
2002-03-12 7:26 ` junkio
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=4656.1015888475@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=eyal@eyal.emu.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.