All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greg KH <greg@kroah.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Introduce PCI <-> CPU address conversion [1/2]
Date: Fri, 15 Oct 2004 07:19:26 +0000	[thread overview]
Message-ID: <20041015071926.GA11457@twiddle.net> (raw)
In-Reply-To: <20041014143924.GP16153@parcelfarce.linux.theplanet.co.uk>

On Thu, Oct 14, 2004 at 03:39:24PM +0100, Matthew Wilcox wrote:
> I can't use it in the symbios driver because it only exists on alpha,
> arm, mips, parisc, ppc, ppc64, sparc64 and v850.  It doesn't exist on
> i386, ia64, x86_64, arm26, cris, h8300, m32r, sh, sh64 or sparc.

So you conclude from 50% of the ports implementing things in a 
particular way that you should invent a totally new interface?
Isn't the obvious solution to implement the existing interface
for the ports that don't have it?


r~

WARNING: multiple messages have this Message-ID (diff)
From: Richard Henderson <rth@twiddle.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greg KH <greg@kroah.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Introduce PCI <-> CPU address conversion [1/2]
Date: Fri, 15 Oct 2004 00:19:26 -0700	[thread overview]
Message-ID: <20041015071926.GA11457@twiddle.net> (raw)
In-Reply-To: <20041014143924.GP16153@parcelfarce.linux.theplanet.co.uk>

On Thu, Oct 14, 2004 at 03:39:24PM +0100, Matthew Wilcox wrote:
> I can't use it in the symbios driver because it only exists on alpha,
> arm, mips, parisc, ppc, ppc64, sparc64 and v850.  It doesn't exist on
> i386, ia64, x86_64, arm26, cris, h8300, m32r, sh, sh64 or sparc.

So you conclude from 50% of the ports implementing things in a 
particular way that you should invent a totally new interface?
Isn't the obvious solution to implement the existing interface
for the ports that don't have it?


r~

  reply	other threads:[~2004-10-15  7:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 12:47 [PATCH] Introduce PCI <-> CPU address conversion [1/2] Matthew Wilcox
2004-10-14 12:47 ` Matthew Wilcox
2004-10-14 12:53 ` Christoph Hellwig
2004-10-14 12:53   ` Christoph Hellwig
2004-10-14 13:53   ` Matthew Wilcox
2004-10-14 13:53     ` Matthew Wilcox
2004-10-14 18:00     ` Christoph Hellwig
2004-10-14 18:00       ` Christoph Hellwig
2004-10-14 18:07       ` Matthew Wilcox
2004-10-14 18:07         ` Matthew Wilcox
2004-10-14 22:37         ` Colin Ngam
2004-10-14 22:37           ` Colin Ngam
2004-10-15  0:36           ` Matthew Wilcox
2004-10-15  0:36             ` Matthew Wilcox
2004-10-14 14:27 ` Ivan Kokshaysky
2004-10-14 14:27   ` Ivan Kokshaysky
2004-10-14 14:39   ` Matthew Wilcox
2004-10-14 14:39     ` Matthew Wilcox
2004-10-15  7:19     ` Richard Henderson [this message]
2004-10-15  7:19       ` Richard Henderson
2004-10-15 10:34       ` Ivan Kokshaysky
2004-10-15 10:34         ` 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=20041015071926.GA11457@twiddle.net \
    --to=rth@twiddle.net \
    --cc=greg@kroah.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    /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.