Re: [PATCH] SCSI hotplug support

[Oliver Neukum <oliver@neukum.name>]

> > It's harder than doing it the simple way. User space really can do
> > nothing but do the call.
>
> Not true, see my last email.  User space can do a *lot* more than just
> make the call to add the device, and as a matter of fact it already does.

But surely it can do more if it can be called with knowledge of a device node,
can't it? Nobody argues against doing a hotplug call. But divorcing
recognisition on the bus and attaching a driver to it seems to be bad
to me. After all there's nothing you can do with a SCSI device without device
node.
Plus you keep a difference between the coldplugging and the hotplugging case,
which is not nice.

> > Plus, you can use such a kernel API to really free the device's
> > memory, because you cannot know when user space, or indeed if, has
> > freed the device.
>
> Not true at all.  Define a revoke/slave_detach entry point to your driver
> and you get called when the device is removed so that you can free up any
> of your resources.

I see.

	Regards
		Oliver