From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevtest conflicts with reality
Date: Wed, 19 Apr 2006 21:04:39 +0000 [thread overview]
Message-ID: <20060419210439.GA22745@kroah.com> (raw)
In-Reply-To: <20060418171520.J25073@chenjesu.americas.sgi.com>
On Wed, Apr 19, 2006 at 10:36:12AM -0500, Brent Casavant wrote:
> On Wed, 19 Apr 2006, Kay Sievers wrote:
>
> > Looks like the driver is not using the driver core properly and you
> > don't pass the dev_t to the class function, which will automatically
> > create the "dev" file in sysfs and add MAJOR=, MINOR= to the event
> > environment. Recent udev versions depend on the variable in the
> > environment and don't open the "dev" file like udevtest is doing it.
>
> OK, I suppose that makes sense. The code currently calls
> class_device_register() before calling cdev_add(). I imagine
> swapping the order of those operations will fix the problem.
>
> Does that sound about right?
Yes, that should do it.
thanks,
greg k-h
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-04-19 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 22:32 udevtest conflicts with reality Brent Casavant
2006-04-19 3:00 ` Andrey Borzenkov
2006-04-19 11:57 ` Kay Sievers
2006-04-19 15:36 ` Brent Casavant
2006-04-19 21:04 ` 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=20060419210439.GA22745@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).