[PATCH 0/2] modesetting: Get rid of unnecessary damage tracking

[Keith Packard]

The modesetting driver has support for informing the kernel driver
about all dirty regions of the screen. Frame buffer drivers like
DisplayLink use this to minimize the amount of data sent over the link
when things change.

Most other framebuffer drivers don't need (or want) this.

The first patch in this series fixes the code which was supposed to
automatically disable damage tracking when the driver didn't support
it; that was broken as it dropped the -ENOSYS error on the floor.

The second patch checks to see whether the driver supports the dirty
ioctl before creating the damage object and hooking it up.