From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Greg KH <greg@kroah.com>,
ink@jurassic.park.msu.ru, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Make hot unplugging of PCI buses work
Date: Mon, 24 Feb 2003 03:10:57 +0300 [thread overview]
Message-ID: <20030224031057.A611@localhost.park.msu.ru> (raw)
In-Reply-To: <20030223193229.F20405@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sun, Feb 23, 2003 at 07:32:29PM +0000
On Sun, Feb 23, 2003 at 07:32:29PM +0000, Russell King wrote:
> Alan kindly sent one of these beasts to me, which renewed my interest
> in this area. I'll forward stuff so far.
If you're talking the Mobility things, I certainly wouldn't mind to
have one ;-) - this stuff isn't available here in Moscow, I did check...
> I'd like to hear Gregs comments first - Greg knows the hotplugging code
> better than me.
Ditto.
> We need to wait until everything is setup for step 4 because we may
> (and do in the case of this split-bridge) need to program PCI-PCI
> bridges before the devices become accessible.
At a glance I agree with your patch.
Ivan.
next prev parent reply other threads:[~2003-02-24 0:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 17:34 [PATCH] Make hot unplugging of PCI buses work Russell King
2003-02-23 18:16 ` Jeff Garzik
2003-02-23 18:57 ` Linus Torvalds
2003-02-23 19:32 ` Russell King
2003-02-23 21:29 ` Alan Cox
2003-02-24 0:10 ` Ivan Kokshaysky [this message]
2003-02-23 21:01 ` Scott Murray
2003-02-23 21:24 ` Russell King
2003-02-23 22:27 ` Scott Murray
2003-02-24 0:59 ` Linus Torvalds
2003-02-24 5:40 ` Scott Murray
2003-02-24 6:08 ` Greg KH
2003-02-24 5:48 ` Greg KH
2003-02-24 10:03 ` Russell King
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=20030224031057.A611@localhost.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.