mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (11/43) Kconfig fix (infiniband and PCI)
Date: Wed, 24 Aug 2005 16:35:49 +0100	[thread overview]
Message-ID: <20050824153549.GJ9322@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050824152609.GB4851@stusta.de>

On Wed, Aug 24, 2005 at 05:26:09PM +0200, Adrian Bunk wrote:
> As I said, on i386.

Builds due to stubs being still present, doesn't do anything since it
doesn't even try to look for any hardware in that case.

> > have PCI at all - same situation as with firewire.  Note that you won't
> > get any low-level drivers on PCI-less config even on i386, so while I
> > agree that more accurate dependency would be nice here (as well as for
> > drivers/ieee1394), for all practical purposes the same dependency works
> > here.
> > 
> > BTW, this is more general question - do we expect pci helpers to be present
> > on all platforms and do we consider their use acceptable in code that does
> > not depend on PCI?
> >...
> 
> Are you talking about the ones that already have dummy functions for the 
> PCI=n case in include/linux/pci.h, or about other functions?

pci_map.../pci_unmap..., for one thing.

  reply	other threads:[~2005-08-24 15:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 21:45 Al Viro
2005-08-24 11:26 ` Adrian Bunk
2005-08-24 14:57   ` Al Viro
2005-08-24 15:26     ` Adrian Bunk
2005-08-24 15:35       ` Al Viro [this message]
2005-08-24 16:22 ` Roland Dreier
2005-08-24 16:31   ` Al Viro
2005-08-24 16:41     ` Al Viro
2005-08-24 17:02       ` Roland Dreier

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=20050824153549.GJ9322@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 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®