https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #99 from mnrzk@protonmail.com --- (In reply to Nicholas Kazlauskas from comment #98)
As much as I'd like to remove the DRM private object from the state instead of just carrying it over I'd really rather not be hacking around behavior from the DRM core itself.
Maybe there's value in adding these as DRM helpers in the case where a driver explicitly wants to remove something from the state. My guess as to why these don't exist today is because they can be bug prone since the core implicitly adds some objects (like CRTCs when you add a plane and CRTCs when you add connectors) but I don't see any technical limitation for not exposing this.
I'm a little bit confused, is there anything particularly illegal or discouraged about the patch I sent? If so, how should I correct it?
Should I create some sort of DRM helper for deleting a private object and use that to delete the state's associated private object?