From: Greg KH <greg@kroah.com>
To: "David S. Miller" <davem@redhat.com>
Cc: benh@kernel.crashing.org, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: Removal of pci_find_* in 2.5
Date: Mon, 15 Jul 2002 17:26:13 -0700 [thread overview]
Message-ID: <20020716002613.GB32431@kroah.com> (raw)
In-Reply-To: <20020714.222527.57270686.davem@redhat.com>
On Sun, Jul 14, 2002 at 10:25:27PM -0700, David S. Miller wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Sat, 13 Jul 2002 15:45:53 +0200
>
> That case shouldn't be a problem, since when your device get discovered,
> hopefully, the host controller is already there. Though in some cases,
> host controllers just appear as a sibling device, and in this specific
> case, it may be not have been "discovered" yet.
>
> THat's not what I'm concerned about, what I care about is that there
> still will be a pci_find_*() I can call to see if DEV/ID is on
> the bus. That is the easiest way to perform that search right
> now.
Yes, it will stay. It is needed for situations just like these, and lots
of other valid reasons.
thanks,
greg k-h
next prev parent reply other threads:[~2002-07-16 0:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 0:36 Greg KH
2002-07-13 2:23 ` Alan Cox
2002-07-13 1:12 ` David S. Miller
2002-07-13 14:46 ` Alan Cox
2002-07-13 20:52 ` David S. Miller
2002-07-13 13:45 ` Benjamin Herrenschmidt
2002-07-15 5:25 ` David S. Miller
2002-07-16 0:26 ` Greg KH [this message]
2002-07-14 20:07 ` Eric W. Biederman
2002-07-16 0:25 ` Greg KH
2002-07-16 10:56 ` Eric W. Biederman
2002-07-16 17:33 ` Patrick Mochel
2002-07-17 12:41 ` Eric W. Biederman
2002-07-13 4:04 Matt_Domsch
2002-07-13 4:41 ` Jeff Garzik
2002-07-13 5:09 ` Greg KH
2002-07-13 14:35 ` Alan Cox
2002-07-13 15:37 ` Jeff Garzik
2002-07-13 17:06 ` Alan Cox
2002-07-13 19:28 ` Jeff Garzik
2002-07-13 19:33 ` Jeff Garzik
2002-07-13 13:13 Matt_Domsch
2002-07-16 19:23 Matt_Domsch
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=20020716002613.GB32431@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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®