The subject doesn't make any sense to me.

But thn again queued sound really weird.  You just have a managed
API with a refcount and synchronization, right?

procfs and debugfs already support these kind of managed ops, kinda sad
to duplicate this concept yet another time.

> +static long cdev_queued_ioctl(struct file *file, unsigned int cmd, unsigned 
> long arg)

Overly long line.

> +__must_check int __cdev_register_queued(struct cdev *cdev, struct module 
> *owner,
> +                                     dev_t dev, unsigned count,
> +                                     const struct cdev_operations *qops)
> +{
> +     int rc;
> +
> +     if (!qops->ioctl || !owner)
> +             return -EINVAL;

Why is the ioctl method mandatory?
_______________________________________________
Linux-nvdimm mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to