Messages in this thread | | | Subject | Re: [patch] kernel sysfs events layer | From | Robert Love <> | Date | Thu, 02 Sep 2004 12:27:49 -0400 |
| |
On Thu, 2004-09-02 at 15:26 +0200, Kay Sievers wrote:
> o What kind of signal do we need? A lazy string, a well defined set like > ADD/REMOVE/CHANGE? > Or can we get rid of the whole signal? But how can we distinguish between > add and remove? Watching if the sysfs file comes or goes is not a option, > I think.
I think (from our off-list discussions) that we really need the signal. Agreed?
I do think that defining the signal to specific values makes sense, e.g. KEVENT_ADD, KEVENT_REMOVE, KEVENT_MOUNTED, etc. We could also send the attribute as a string.
To get around the hotplug issue that would occur without 'enum kevent', as we discussed, we could have a "hotplug_added" signal or whatever. Nothing wrong with that.
Cool or not?
Robert Love
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |