On Wed, Feb 22, 2017 at 12:29:11PM +0200, Joonas Lahtinen wrote: > On ke, 2017-02-22 at 10:11 +0000, Chris Wilson wrote: > > On Wed, Feb 22, 2017 at 12:06:35PM +0200, Jani Nikula wrote: > > > > > > > > On Tue, 21 Feb 2017, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> 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). > > > > > > > > v2: Use __always_inline and __builtin_strcmp > > > > > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > > > Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> > > > > > > Reviewed-by: Jani Nikula <jani.nikula@xxxxxxxxx> > > > > Joonas, do we feel justified in pushing now that Jani has a pending > > usecase? > > -Chris > > Seems reasonable. Then pushed. Have fun Jani! -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
