public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Roland Dreier <rolandd@cisco.com>
Cc: Al Viro <viro@www.linux.org.uk>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (11/43) Kconfig fix (infiniband and PCI)
Date: Wed, 24 Aug 2005 17:41:33 +0100	[thread overview]
Message-ID: <20050824164133.GL9322@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050824163134.GK9322@parcelfarce.linux.theplanet.co.uk>

On Wed, Aug 24, 2005 at 05:31:34PM +0100, Al Viro wrote:
> On Wed, Aug 24, 2005 at 09:22:27AM -0700, Roland Dreier wrote:
> >     Al> infiniband uses PCI helpers all over the place (including the
> >     Al> core parts) and won't build without PCI.
> > 
> > I don't think this is the right fix.  The only PCI helpers used in
> > code that is enabled with CONFIG_PCI=n are pci_unmap_addr_set() and
> > pci_unmap_addr().  And they're only used because no one has added
> > dma_unmap_addr_set() and dma_unmap_addr() -- the core code is properly
> > using the general dma_xxx API wherever possible.
> > 
> > There actually is non-PCI InfiniBand hardware coming, so we'll have to
> > fix this properly at some point.
> 
> I'm all for it and removing BROKEN from Kconfig when fixes happen is
> obviously not a problem at all ;-)

PS: note that it's not
	depends on PCI
it's
	depends on PCI || BROKEN
which
	a) documents that something is wrong
	b) leaves all setups usable now intact
	c) prevents broken setups from being picked.

I certainly agree that proper fix is to switch to dma_... - no arguments here.
BTW, another dubious thing is use of DECLARE_PCI_UNMAP_ADDR() in infiniband
core - it's fine in PCI drivers (which is how it's used elsewhere), but not
in generic data structures.

  reply	other threads:[~2005-08-24 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 21:45 [PATCH] (11/43) Kconfig fix (infiniband and PCI) 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
2005-08-24 16:22 ` Roland Dreier
2005-08-24 16:31   ` Al Viro
2005-08-24 16:41     ` Al Viro [this message]
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=20050824164133.GL9322@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolandd@cisco.com \
    --cc=torvalds@osdl.org \
    --cc=viro@www.linux.org.uk \
    /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