From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org, David Mosberger <davidm@hpl.hp.com>
Subject: Re: [PATCH] [3/3] PCI segment support
Date: Mon, 9 Jun 2003 15:26:16 +0400 [thread overview]
Message-ID: <20030609152616.D15283@jurassic.park.msu.ru> (raw)
In-Reply-To: <20030609111739.GP28581@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Mon, Jun 09, 2003 at 12:17:39PM +0100
On Mon, Jun 09, 2003 at 12:17:39PM +0100, Matthew Wilcox wrote:
> hmm, yes, well. There's a certain amount of sloppiness allowed with
> it being a macro, in that bus->sysdata and dev->sysdata have the same
> value so it works both ways.
Well, it's true for many architectures, but not for all.
IIRC, bus->sysdata != dev->sysdata on sparc and parisc.
> Of course, this prohibits any architecture
> from implementing it as a function, so we really should make up our minds
> which it is to be. It sounds like bus is more generally useful than dev,
> so I'll make that explicit.
Great.
Ivan.
next prev parent reply other threads:[~2003-06-09 11:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 23:44 Matthew Wilcox
2003-04-08 16:38 ` Ivan Kokshaysky
2003-04-08 16:50 ` Matthew Wilcox
2003-04-08 17:21 ` Ivan Kokshaysky
2003-04-08 17:31 ` Matthew Wilcox
2003-04-09 5:41 ` Grant Grundler
2003-06-08 16:43 ` Matthew Wilcox
2003-06-08 21:33 ` Russell King
2003-06-08 23:16 ` Alan Cox
2003-06-09 10:07 ` Ivan Kokshaysky
2003-06-09 10:20 ` David S. Miller
2003-06-09 10:42 ` Ivan Kokshaysky
2003-06-09 10:43 ` David S. Miller
2003-06-09 11:00 ` Ivan Kokshaysky
2003-06-09 11:04 ` David S. Miller
2003-06-09 11:17 ` Matthew Wilcox
2003-06-09 11:26 ` Ivan Kokshaysky [this message]
2003-06-09 14:34 ` Matthew Wilcox
2003-06-09 11:41 ` Ivan Kokshaysky
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=20030609152616.D15283@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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®