All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Greg KH <greg@kroah.com>, "Martin J. Bligh" <mbligh@aracnet.com>,
	Matthew Dobson <colpatch@us.ibm.com>,
	linux-kernel@vger.kernel.org, hohnbaum@us.ibm.com,
	mochel@osdl.org
Subject: Re: [0/4] NUMA-Q: remove PCI bus number mangling
Date: Wed, 1 Jan 2003 01:28:57 -0800	[thread overview]
Message-ID: <20030101092857.GO9704@holomorphy.com> (raw)
In-Reply-To: <20021113112028.GI23425@holomorphy.com>

On Tue, Nov 12, 2002 at 04:20:32PM -0800, Greg KH wrote:
>>> Ok, then also please fix up drivers/pci/probe.c::pci_setup_device() to
>>> set a unique slot_name up for the pci_dev, if you have multiple
>>> domains/segments.

On Wed, Nov 13, 2002 at 02:10:05AM -0800, William Lee Irwin III wrote:
>> Reporting that stuff is trivial, but resolving the deep arch issues
>> with the remaining failures I'm getting (not directly bus-related,
>> actually I/O resource allocation going wrong) have me badly stumped.
>> Push back that ETA to weeks. I'll break off generically mergeable
>> bits and send them your way as I go though. The patch queue is
>> something like 20 long, but most of the content is "resolve one
>> problem after the other". Getting this into a state of "the system
>> works at every step of the way" is tricky, esp. since the end results
>> of today's excursion do not yet include a fully-working system.

On Wed, Nov 13, 2002 at 03:20:28AM -0800, William Lee Irwin III wrote:
> Actually benh has straightened me out on this count as of a few minutes
> ago. Something will probably show up here by Friday.

I've had a lot of trouble with this. Don't count on this anytime soon.

Bill

  reply	other threads:[~2003-01-01  9:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 12:37 [0/4] NUMA-Q: remove PCI bus number mangling William Lee Irwin III
2002-11-12 20:52 ` William Lee Irwin III
2002-11-12 20:55   ` William Lee Irwin III
2002-11-12 21:29   ` Matthew Dobson
2002-11-12 21:35     ` William Lee Irwin III
2002-11-12 21:39       ` William Lee Irwin III
2002-11-12 22:46         ` Martin J. Bligh
2002-11-12 21:53           ` William Lee Irwin III
2002-11-12 23:53             ` Martin J. Bligh
2002-11-12 22:59               ` William Lee Irwin III
2002-11-12 23:19                 ` William Lee Irwin III
2002-11-12 23:58                 ` William Lee Irwin III
2002-11-13  0:04                   ` Greg KH
2002-11-13  0:12                     ` William Lee Irwin III
2002-11-13  0:20                       ` Greg KH
2002-11-13  0:28                         ` William Lee Irwin III
2002-11-13  1:01                           ` William Lee Irwin III
2002-11-13 12:07                           ` Ivan Kokshaysky
2002-11-13 20:59                             ` William Lee Irwin III
2002-11-13 10:10                         ` William Lee Irwin III
2002-11-13 11:20                           ` William Lee Irwin III
2003-01-01  9:28                             ` William Lee Irwin III [this message]
2002-11-12 21:48       ` William Lee Irwin III
2002-11-12 21:48       ` William Lee Irwin III
2002-11-12 20:53 ` William Lee Irwin III

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=20030101092857.GO9704@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=colpatch@us.ibm.com \
    --cc=greg@kroah.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mochel@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 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.