All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, bcollins@debian.org,
	linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/3] raw1394: sysfs support via class_simple
Date: Wed, 17 Nov 2004 12:30:09 +0000	[thread overview]
Message-ID: <419B4451.3010104@gentoo.org> (raw)
In-Reply-To: <200411140142.56071.dtor_core@ameritech.net>

Dmitry Torokhov wrote:
> Hmm, with the exception of raw1394, the rest of ieee1394 subsystem does
> not need its own classes as 1394 devices hook up into other subsystems
> (SCSI, NET) and are classified with the rest of the devices in those
> systems. After all userspace does not really care whether eth0 is on
> PCI, ISA or IEEE1394, all it needs to know that it is just another network
> interface. Am I missing something?

No, I think I was. I was trying to follow the way that USB does it (e.g. usblp 
linking into the usb sysfs class) but I think you are right - IEEE1394 is in a 
different situation. raw1394 is the only ieee1394 driver (as far as I can see) 
that might benefit fitting into a generic class. I think we should stick with 
class_simple and possibly consider a generic class if more drivers might 
require it in the future.

Daniel

      reply	other threads:[~2004-11-17 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14  3:37 [PATCH 3/3] raw1394: sysfs support via class_simple Daniel Drake
2004-11-14  6:42 ` Dmitry Torokhov
2004-11-17 12:30   ` Daniel Drake [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=419B4451.3010104@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=bcollins@debian.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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.