public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Dave Boutcher <sleddog@us.ibm.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ibmvscsi driver - sixth version
Date: Wed, 31 Mar 2004 19:10:34 -0500	[thread overview]
Message-ID: <406B5DFA.80201@pobox.com> (raw)
In-Reply-To: <opr5q28vkql6e53g@us.ibm.com>

Dave Boutcher wrote:
> There will always be 1 (no more, no less) of these struct devices in the
> system, so I'll move the definition of this into iSeries_iommu and then
> just reference it from the driver.  I think that should abstract things
> sufficiently.


Sounds like a small module declaring devices such as this would be more 
appropriate than unrelated iommu code?

In a regular PCI system, the PCI bus probing code creates devices.  For 
platform-specific virtual devices, ppc64 needs "create my virtual 
devices" initialization code, it looks like.

	Jeff




  reply	other threads:[~2004-04-01  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <opr3u0ffo7l6e53g@us.ibm.com>
     [not found] ` <20040225134518.A4238@infradead.org>
     [not found]   ` <opr3xta6gbl6e53g@us.ibm.com>
     [not found]     ` <1079027038.2820.57.camel@mulgrave>
2004-03-31 21:26       ` [PATCH] ibmvscsi driver - sixth version Dave Boutcher
2004-03-31 21:58         ` James Bottomley
2004-03-31 22:37           ` Dave Boutcher
2004-03-31 22:02         ` Jeff Garzik
2004-03-31 23:12           ` Dave Boutcher
2004-03-31 23:39             ` James Bottomley
2004-03-31 23:51               ` Dave Boutcher
2004-04-01  0:10                 ` Jeff Garzik [this message]
2004-04-01  0:16             ` Jeff Garzik

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=406B5DFA.80201@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sleddog@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox