Re: Device count (to be done with)

[Stamatis Mitrofanis <ewstam@softhome.net>]

Oliver Neukum wrote:

>>The "should" count should be mostly managed from userspace (but also
>>give the option for modules to change it) and user space programs must
>>not care about anything beyond modprobe. For uniformity, better put this
>>"should" count right next to the "must" (use) count.
>>
>Here I must disagree. You need to add more code to the kernel to return 
>information on successfully binding drivers to devices to user space than by 
>simply handling the counter.
>
Of course, I understand that this system must be as robust as possible, 
but I was viewing things from the most global perspective. I mean I was 
only referring to "kernel modules" rather than devices. My thoughts were 
as simple as "two module loads will result in the module actually being 
uloaded only after two module unloads". I was just referring to module 
"convenience" counts which would be very useful (even necessary) to 
have. Now, if there need to be subsystem-specific error-handling 
mechanisms that's fine (the agent scripts can very well work with this).

Though a problem is that I'm surely not the most "qualified" person to 
make a patch for it since I'm not familiar with the kernel's insides (it 
would take me too long). I'd be very satisfied to hear that somebody is 
working on it.

(sorry for mentioning this over and over again but...)


_______________________________________________
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