Message ID | 20220314224253.236359-1-dmitry.osipenko@collabora.com (mailing list archive) |
---|---|
Headers | show |
Series | Add memory shrinker to VirtIO-GPU DRM driver | expand |
On Mon, 14 Mar 2022 at 22:44, Dmitry Osipenko <dmitry.osipenko@collabora.com> wrote: > Dmitry Osipenko (8): > drm/virtio: Correct drm_gem_shmem_get_sg_table() error handling > drm/virtio: Check whether transferred 2D BO is shmem > drm/virtio: Unlock GEM reservations in error code path These three are legitimate fixes that we want regardless of the shrinker. Please add the respective "Fixes" tag, so they find their way in the stable trees. With that, them 3 are: Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com> HTH Emil
On 3/15/22 15:47, Emil Velikov wrote: > On Mon, 14 Mar 2022 at 22:44, Dmitry Osipenko > <dmitry.osipenko@collabora.com> wrote: > >> Dmitry Osipenko (8): >> drm/virtio: Correct drm_gem_shmem_get_sg_table() error handling >> drm/virtio: Check whether transferred 2D BO is shmem >> drm/virtio: Unlock GEM reservations in error code path > > These three are legitimate fixes that we want regardless of the shrinker. > > Please add the respective "Fixes" tag, so they find their way in the > stable trees. With that, them 3 are: > Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com> Thank you, I already added stable tag to the first patch. The other patches aren't critical for the stable kernels, IMO, but we can tag them too for completeness. I'll do in v3.