Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	greg@kroah.com, Ladislav Michl <ladis@linux-mips.org>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com,
	ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: [2.6 patch] 2.6.10-mm2: let I2C_ALGO_SGI depend on MIPS
Date: Thu, 6 Jan 2005 19:15:20 +0100	[thread overview]
Message-ID: <20050106181519.GG3096@stusta.de> (raw)
In-Reply-To: <20050106002240.00ac4611.akpm@osdl.org>

On Thu, Jan 06, 2005 at 12:22:40AM -0800, Andrew Morton wrote:
>...
> All 560 patches:
>...
> bk-i2c.patch
>...


There's no reason for offering a MIPS-only driver on other architectures 
(even though it does compile).

Even better dependencies on specific MIPS variables might be possible 
that obsolete this patch, but this patch fixes at least the !MIPS case.


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.10-mm2-full/drivers/i2c/algos/Kconfig.old	2005-01-06 19:07:16.000000000 +0100
+++ linux-2.6.10-mm2-full/drivers/i2c/algos/Kconfig	2005-01-06 19:08:22.000000000 +0100
@@ -61,7 +61,7 @@
 
 config I2C_ALGO_SGI
 	tristate "I2C SGI interfaces"
-	depends on I2C
+	depends on I2C && MIPS
 	help
 	  Supports the SGI interfaces like the ones found on SGI Indy VINO
 	  or SGI O2 MACE.

       reply	other threads:[~2005-01-06 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050106002240.00ac4611.akpm@osdl.org>
2005-01-06 18:15 ` Adrian Bunk [this message]
2005-01-06 19:27   ` [2.6 patch] 2.6.10-mm2: let I2C_ALGO_SGI depend on MIPS Ralf Baechle
2005-01-06 19:35     ` Ilya A. Volynets-Evenbakh
2005-01-06 19:46       ` Greg KH
2005-01-07  9:12         ` Ladislav Michl
2005-01-07 19:14           ` Greg KH

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=20050106181519.GG3096@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=ladis@linux-mips.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=sensors@stimpy.netroedge.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