From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: registering same sysfs class in different drivers.
Date: Sat, 17 Jan 2004 00:09:16 +0000 [thread overview]
Message-ID: <20040117000916.GA3698@kroah.com> (raw)
In-Reply-To: <20040116064233.78134.qmail@web14915.mail.yahoo.com>
On Thu, Jan 15, 2004 at 10:42:33PM -0800, Jon Smirl wrote:
> The DRI drivers for each card type are indepenent from each other, but they all
> exist in the same sysfs class. Right now when I try to load a second driver I'm
> faulting in sysfs:create_dir with parent dentry NULL. create_dir() is called via
> simple_add_class_device(). Either driver loads standalone without problem.
>
> I suspect the fault is because each driver is registering it's own copy of the
> 'dri' class. Is there some mechanism to see if the class has already been
> registered and use the preexisting copy? class_register() always returns 0.
Yes, you can't register two classes with the same name.
But that should have given you an error, care to fix that up and send me
a patch?
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-01-17 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 6:42 registering same sysfs class in different drivers Jon Smirl
2004-01-16 19:51 ` Jon Smirl
2004-01-17 0:09 ` Greg KH [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=20040117000916.GA3698@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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 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.