public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jes Sorensen <jes@sgi.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	"'Keith Owens'" <kaos@sgi.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let IA64_GENERIC select more stuff
Date: Thu, 9 Feb 2006 06:18:02 -0700	[thread overview]
Message-ID: <20060209131802.GE1593@parisc-linux.org> (raw)
In-Reply-To: <yq0zml0lmmg.fsf@jaguar.mkp.net>

On Thu, Feb 09, 2006 at 07:53:11AM -0500, Jes Sorensen wrote:
> There's other reasons why this is a moot exercise anyway, allyesconfig
> doesn't link on ia64 due to the size of the object exceeding the reach
> of the relative link relocs. Not much you can do about that.

That'd be a toolchain problem then ... need to insert stubs.

> - HP100 driver cannot be compiled on systems without ISA support in it's
>   current state.

I have it enabled on parisc without ISA or EISA.  More details, please.

>  config HP100
>  	tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
> -	depends on NET_ETHERNET && (ISA || EISA || PCI)
> +	depends on NET_ETHERNET && ISA || EISA
>  	help

Also I think this is wrong.  Doesn't the precedence make this evaluate
as (NET_ETHERNET && ISA) || EISA ?

  reply	other threads:[~2006-02-09 13:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 22:11 [2.6 patch] IA64_GENERIC shouldn't select other stuff Adrian Bunk
2006-02-07 22:37 ` Keith Owens
2006-02-07 22:43   ` Matthew Wilcox
2006-02-07 22:53     ` Adrian Bunk
2006-02-07 23:17   ` [2.6 patch] let IA64_GENERIC select more stuff Adrian Bunk
2006-02-08  0:52     ` Chen, Kenneth W
2006-02-08  1:19       ` Adrian Bunk
2006-02-08  1:40         ` Chen, Kenneth W
2006-02-08  2:08           ` Adrian Bunk
2006-02-08  2:17             ` Chen, Kenneth W
2006-02-08  2:43               ` Adrian Bunk
2006-02-08  2:48           ` Keith Owens
2006-02-08  2:54             ` Matthew Wilcox
2006-02-08  2:58             ` Chen, Kenneth W
2006-02-08  3:51               ` Adrian Bunk
2006-02-08  5:52                 ` Chen, Kenneth W
2006-02-08 11:59                   ` Adrian Bunk
2006-02-08 13:38                     ` Jes Sorensen
2006-02-08 21:38                       ` Adrian Bunk
2006-02-08 22:24                         ` Chen, Kenneth W
2006-02-08 22:49                           ` Adrian Bunk
2006-02-09 12:53                         ` Jes Sorensen
2006-02-09 13:18                           ` Matthew Wilcox [this message]
2006-02-09 13:26                             ` Jes Sorensen
2006-02-09 14:16                               ` Adrian Bunk
2006-02-09 15:19                                 ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2006-02-08 18:35 Luck, Tony
2006-02-08 19:21 ` Alex Williamson
2006-02-08 19:24   ` Jes Sorensen
2006-02-08 19:55     ` Chen, Kenneth W
2006-02-08 21:24       ` Matthew Wilcox
2006-02-08 21:36         ` Chen, Kenneth W
2006-02-08 19:48 Luck, Tony
2006-02-08 22:35 Luck, Tony

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=20060209131802.GE1593@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bunk@stusta.de \
    --cc=jes@sgi.com \
    --cc=kaos@sgi.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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