public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Couple of I2O sysfs changes
Date: Tue, 13 Sep 2005 14:06:54 -0500	[thread overview]
Message-ID: <d120d5000509131206635b04e2@mail.gmail.com> (raw)
In-Reply-To: <4326AAF8.2060702@shadowconnect.com>

On 9/13/05, Markus Lidel <Markus.Lidel@shadowconnect.com> wrote:
> > Also, it looks like i2o_device_class itself is not needed - correct
> > me if I am wrong, but all i2o devics reside on their own bus so
> > i2o_devices class simply mirrors iformation from the bus and can
> > also be safely removed.
> 
> Nope, there is one bus per controller not per device...
> 

That is what I was trying to say. Well, not exactly... What I was
really trying to say is AFAIKS I2O system registers only one sysfs bus
object and all I2O devices reside on it. Unlike, for exaple input
objects, that can appear on serio, gameport, usb buses and so on. So
if one wants to see all I2O devices in sysfs he could just check
/sys/bus/i2o/devices/ and see them all there.

-- 
Dmitry

      reply	other threads:[~2005-09-13 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  4:31 [PATCH 0/2] Couple of I2O sysfs changes Dmitry Torokhov
2005-09-13  4:34 ` [PATCH 1/2] I2O: remove i2o_device_class_interface Dmitry Torokhov
2005-09-13  4:34   ` [PATCH 1/2] I2O: remove i2o_device_class Dmitry Torokhov
2005-09-13 10:33 ` [PATCH 0/2] Couple of I2O sysfs changes Markus Lidel
2005-09-13 19:06   ` Dmitry Torokhov [this message]

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=d120d5000509131206635b04e2@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=Markus.Lidel@shadowconnect.com \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.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