On Wed, Dec 10, 2014 at 04:48:20PM +0100, Andrzej Hajda wrote:
> restrack framework allows tracking presence of resources with dynamic life
> time. Typical example of such resources are all resources provided by device
I don't know about anyone else but I'm having a hard time reading the
restrack name, it looks like a misspelling of restack to me.
At a high level my biggest questions here are the relationship between
this and the component code and usability. The usability concern I have
is that I see no diagnostics or trace here at all. This means that if a
user looks at their system, sees that the device model claims the driver
for a device bound to the device but can't see any sign of the device
doing anything they don't have any way of telling why that is other than
to look in the driver code, see what resources it was trying to depend
on and then go back to the running system to try to understand which of
those resources hasn't appeared.
> +int restrack_up(unsigned long type, const void *id, void *data)
> +int restrack_down(unsigned long type, const void *id, void *data)
Again I'm not sure that the up and down naming is meaningful in the
context of this interface.
> +static void restrack_itb_cb(struct track_block *itb, void *data, bool on)
> +{
itb_cb?
Attachment:
signature.asc
Description: Digital signature
