On Thu, Dec 15, 2016 at 12:36:02PM +0100, Thierry Reding wrote: > From: Thierry Reding <treding@xxxxxxxxxx> > > drm_event_reserve_init_locked() is the correct function to call when > already holding the dev->event_lock lock. > > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx> Pushed to drm-misc-next, thanks. -Daniel > --- > drivers/gpu/drm/drm_fops.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/drm_fops.c b/drivers/gpu/drm/drm_fops.c > index 5d96de40b63f..48e106557c92 100644 > --- a/drivers/gpu/drm/drm_fops.c > +++ b/drivers/gpu/drm/drm_fops.c > @@ -622,7 +622,7 @@ EXPORT_SYMBOL(drm_event_reserve_init_locked); > * kmalloc and @p must be the first member element. > * > * Callers which already hold dev->event_lock should use > - * drm_event_reserve_init() instead. > + * drm_event_reserve_init_locked() instead. > * > * RETURNS: > * > -- > 2.10.2 > > _______________________________________________ > dri-devel mailing list > dri-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
