Hi
Am 15.11.21 um 18:00 schrieb Zack Rusin:
On Mon, 2021-11-15 at 13:55 +0100, Thomas Zimmermann wrote:
Besides some legacy code, vmwgfx is the only user of DRM's hash-
table implementation. Copy the code into the driver, so that the
core code can be retired.
No functional changes. However, th
Hi Sam
Am 15.11.21 um 17:27 schrieb Sam Ravnborg:
Hi Thomas,
On Mon, Nov 15, 2021 at 01:55:38PM +0100, Thomas Zimmermann wrote:
Besides some legacy code, vmwgfx is the only user of DRM's hash-
table implementation. Copy the code into the driver, so that the
core code can be retired.
For the r
On Mon, 2021-11-15 at 13:55 +0100, Thomas Zimmermann wrote:
> Besides some legacy code, vmwgfx is the only user of DRM's hash-
> table implementation. Copy the code into the driver, so that the
> core code can be retired.
>
> No functional changes. However, the real solution for vmwgfx is to
> use
Hi Thomas,
On Mon, Nov 15, 2021 at 01:55:38PM +0100, Thomas Zimmermann wrote:
> Besides some legacy code, vmwgfx is the only user of DRM's hash-
> table implementation. Copy the code into the driver, so that the
> core code can be retired.
For the record - I have no clue what legacy code uses the
On Mon, Nov 15, 2021 at 01:55:38PM +0100, Thomas Zimmermann wrote:
> Besides some legacy code, vmwgfx is the only user of DRM's hash-
> table implementation. Copy the code into the driver, so that the
> core code can be retired.
>
> No functional changes. However, the real solution for vmwgfx is t
