From: Randy Dunlap <rdunlap@xenotime.net>
To: Brent Casavant <bcasavan@sgi.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Jeremy Higdon <jeremy@sgi.com>, Pat Gefre <pfg@sgi.com>
Subject: Re: [PATCH 2/2] ioc4: Enable build on non-SN2
Date: Tue, 10 Oct 2006 10:39:15 -0700 [thread overview]
Message-ID: <20061010103915.f412d770.rdunlap@xenotime.net> (raw)
In-Reply-To: <20061010120928.V71367@pkunk.americas.sgi.com>
On Tue, 10 Oct 2006 12:11:16 -0500 (CDT) Brent Casavant wrote:
> Index: top/drivers/Kconfig
> ===================================================================
> --- top.orig/drivers/Kconfig 2006-10-09 17:41:25.000000000 -0500
> +++ top/drivers/Kconfig 2006-10-09 17:47:50.415607888 -0500
> @@ -14,6 +14,10 @@
>
> source "drivers/block/Kconfig"
>
> +# misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
> +
> +source "drivers/misc/Kconfig"
> +
> source "drivers/ide/Kconfig"
>
> source "drivers/scsi/Kconfig"
> @@ -52,8 +56,6 @@
>
> source "drivers/hwmon/Kconfig"
>
> -source "drivers/misc/Kconfig"
> -
> source "drivers/mfd/Kconfig"
>
> source "drivers/media/Kconfig"
Mostly curious: did you observe that this is required?
I always thought that Roman said that unknown config variables
caused a rescan by kconfig. IOW, I thought that it wouldn't
be observable by a user. Just wondering..
> Index: top/drivers/misc/Kconfig
> ===================================================================
> --- top.orig/drivers/misc/Kconfig 2006-10-09 17:41:25.000000000 -0500
> +++ top/drivers/misc/Kconfig 2006-10-09 17:48:56.555631075 -0500
> @@ -28,6 +28,18 @@
>
> If unsure, say N.
>
> +config SGI_IOC4
> + tristate "SGI IOC4 Base IO support"
> + default m
> + ---help---
> + This option enables basic support for the IOC4 chip on certain
> + SGI IO controller cards (IO9, IO10, and PCI-RT). This option
> + does not enable any specific functions on such a card, but provides
> + necessary infrastructure for other drivers to utilize.
> +
> + If you have an SGI Altix with an IOC4-based card say Y.
> + Otherwise say N.
The lines under ---help--- should be indented by 2 spaces (by
convention) (and even though they were not when in the /sn/ subdir).
> config TIFM_CORE
> tristate "TI Flash Media interface support (EXPERIMENTAL)"
> depends on EXPERIMENTAL
---
~Randy
next prev parent reply other threads:[~2006-10-10 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 17:11 Brent Casavant
2006-10-10 17:39 ` Randy Dunlap [this message]
2006-10-10 18:21 ` Brent Casavant
2006-10-10 18:53 ` Jan Engelhardt
2006-10-10 19:06 ` Brent Casavant
2006-10-10 19:06 ` Randy Dunlap
2006-10-10 18:26 ` Brent Casavant
2006-10-12 0:23 ` Andrew Morton
2006-10-12 17:16 ` Brent Casavant
2006-10-12 19:37 ` Brent Casavant
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=20061010103915.f412d770.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.com \
/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®