On 06/07, Daniel Vetter wrote: > The crc core code can cope with some late crc, the race is kinda > unavoidable. So no need to flush pending workers, they'll complete in > time. > > Signed-off-by: Daniel Vetter > Cc: Rodrigo Siqueira > Cc: Haneen Mohammed > Cc: Daniel Vetter > --- > drivers/gpu/drm/vkms/vkms_crc.c | 3 --- > 1 file changed, 3 deletions(-) > > diff --git a/drivers/gpu/drm/vkms/vkms_crc.c b/drivers/gpu/drm/vkms/vkms_crc.c > index 96806cd35ad4..9d15e5e85830 100644 > --- a/drivers/gpu/drm/vkms/vkms_crc.c > +++ b/drivers/gpu/drm/vkms/vkms_crc.c > @@ -249,9 +249,6 @@ int vkms_set_crc_source(struct drm_crtc *crtc, const char *src_name) > > ret = vkms_crc_parse_source(src_name, &enabled); > > - /* make sure nothing is scheduled on crtc workq */ > - flush_workqueue(out->crc_workq); > - > spin_lock_irq(&out->lock); > out->crc_enabled = enabled; > spin_unlock_irq(&out->lock); > -- > 2.20.1 > Hi, I tried to apply this patch, but git complained about it. I fixed the problem manually (it was very simple), but I noticed that dim did not add the tag "Link". Because of this, I decided to check with you before I apply this patch. Is it ok to fix conflict without dim? Is it ok apply a patch without the tag Link? -- Rodrigo Siqueira https://siqueira.tech