From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: ink@jurassic.park.msu.ru, andrew.grover@intel.com,
mochel@osdl.org, Greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: pci segments/domains
Date: Fri, 17 May 2002 10:42:44 -0400 [thread overview]
Message-ID: <3CE516E4.4000500@mandrakesoft.com> (raw)
In-Reply-To: <3CE512A7.70202@mandrakesoft.com> <20020517.071633.67125480.davem@redhat.com> <3CE514B6.6070302@mandrakesoft.com> <20020517.072625.29433758.davem@redhat.com>
David S. Miller wrote:
> From: Jeff Garzik <jgarzik@mandrakesoft.com>
> Date: Fri, 17 May 2002 10:33:26 -0400
>
> My main want is cosmetic -- call a spade a spade, so to speak.
> s/sysdata/pci_domain/ But doing so opens the door to increased
> flexibility. Later steps can add common members needed by pci-to-pci
> IOMMU tricks which are common to most platforms.
>
>Since the name really doesn't matter let's call it struct pci_controller
>since that is what Alpha and Sparc use already :-)
>
Makes sense, sure :) I just want to get rid of the untyped sysdata in
favor of a struct with a defined type (arch-defined... but named and
defined nonetheless).
Jeff
next prev parent reply other threads:[~2002-05-17 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 2:07 pci segments/domains Grover, Andrew
2002-05-14 2:08 ` David S. Miller
2002-05-16 19:33 ` Jeff Garzik
2002-05-17 1:31 ` David S. Miller
2002-05-16 23:10 ` Pavel Machek
2002-05-17 10:47 ` Ivan Kokshaysky
2002-05-17 10:40 ` David S. Miller
2002-05-17 11:11 ` Ivan Kokshaysky
2002-05-17 11:04 ` David S. Miller
2002-05-17 11:39 ` Ivan Kokshaysky
2002-05-17 11:41 ` David S. Miller
2002-05-17 12:26 ` Ivan Kokshaysky
2002-05-17 12:15 ` David S. Miller
2002-05-17 14:24 ` Jeff Garzik
2002-05-17 14:16 ` David S. Miller
2002-05-17 14:33 ` Jeff Garzik
2002-05-17 14:26 ` David S. Miller
2002-05-17 14:42 ` Jeff Garzik [this message]
2002-05-17 16:24 ` Ivan Kokshaysky
2002-05-17 16:53 ` David S. Miller
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=3CE516E4.4000500@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Greg@kroah.com \
--cc=andrew.grover@intel.com \
--cc=davem@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--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.