The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] iSeries virtual i/o sysfs files
Date: Tue, 22 Jun 2004 12:31:03 +0100	[thread overview]
Message-ID: <20040622113103.GA1288@infradead.org> (raw)
In-Reply-To: <20040622212319.2a0c121b.sfr@canb.auug.org.au>

On Tue, Jun 22, 2004 at 09:23:19PM +1000, Stephen Rothwell wrote:
> What it means is that, as the patch stands, a node is created in
> /sys/devices/vio (and /sys/bus/vio/devices) for all possible virtual
> devices not just those actually present.  The exception is for virtual
> ethernets which are relatively easy to enumerate.  To enumerate the other
> devices precisely, I will need to extract the device probing code from
> each of the other device drivers (viodasd, viocd and viotape) and include
> some (hopefully simplified) form of the code directly into the bus probing
> code for iSeries in vio.c.

Maybe you should just kick your collegues on the OS/400 side to provide
a better interface?  After IBM is oh so Linux friendly they could maybe
fi up their legacy codebases to make the slightest bit of sense?

  reply	other threads:[~2004-06-22 11:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22  4:04 [RFC] iSeries virtual i/o sysfs files Stephen Rothwell
2004-06-22  6:20 ` Jeff Garzik
2004-06-22 11:23   ` Stephen Rothwell
2004-06-22 11:31     ` Christoph Hellwig [this message]
2004-06-22 12:34       ` Stephen Rothwell
2004-06-22 12:39         ` Christoph Hellwig
2004-06-22 13:57     ` Arnd Bergmann

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=20040622113103.GA1288@infradead.org \
    --to=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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