On Mon, Feb 06, 2017 at 02:32:17PM +0200, Joonas Lahtinen wrote: > 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? Merged upto this point until we have a use for new parameter types. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
