linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	Jeff Garzik <jgarzik@pobox.com>, Greg KH <greg@kroah.com>,
	Jiri Slaby <jirislaby@gmail.com>, Greg KH <gregkh@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-ide@vger.kernel.org,
	B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: [PATCH] include: pci_find_device remove (include/asm-i386/ide.h)
Date: Mon, 12 Sep 2005 11:17:21 +0100	[thread overview]
Message-ID: <1126520241.30449.42.camel@localhost.localdomain> (raw)
In-Reply-To: <20050911013004.GI4770@parisc-linux.org>

On Sad, 2005-09-10 at 19:30 -0600, Matthew Wilcox wrote:
> > Lots of them. We also want to know if PCI is present so we can know
> > whether to do the IDE tertiary scan which isn't safe on a PCI bus box.
> 
> surely this is worthy of a comment in the code.  there's at least 3
> people on the cc who're confused bby what it's for.

Thats because someone removed the obvious pci_present() function some
time ago.

Alan


  reply	other threads:[~2005-09-12  9:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 20:32 [PATCH] include: pci_find_device remove (include/asm-i386/ide.h) Jiri Slaby
2005-09-10 20:55 ` Jeff Garzik
2005-09-10 21:19   ` Greg KH
2005-09-10 21:24     ` Jiri Slaby
2005-09-10 21:39     ` Jeff Garzik
2005-09-10 22:33       ` Matthew Wilcox
2005-09-10 23:35         ` Jeff Garzik
2005-09-11  0:34           ` Grant Grundler
2005-09-11  0:47             ` Jeff Garzik
2005-09-11  1:06             ` Alan Cox
2005-09-11  1:24               ` Grant Grundler
2005-09-11  1:30               ` Matthew Wilcox
2005-09-12 10:17                 ` Alan Cox [this message]
2005-09-12 11:21                   ` Matthew Wilcox
2005-09-12 12:35                     ` Alan Cox
2005-09-11  0:06     ` Alan Cox
2005-10-06 22:24   ` Jiri Slaby

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=1126520241.30449.42.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=grundler@parisc-linux.org \
    --cc=jgarzik@pobox.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    /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;
as well as URLs for NNTP newsgroup(s).