On ma, 2017-02-06 at 09:51 +0000, Chris Wilson wrote: > Handling the dynamic charp module parameter requires us to copy it for > the error state, or remember to lock it when reading (in case it used > with 0600). > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> I'm bit hesitant that we merge known dead code here. Maybe the guc firmware path override would be useful to excercise this? Code itself; Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> Regards, Joonas -- Joonas Lahtinen Open Source Technology Center Intel Corporation _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
