Messages in this thread | | | Date | Thu, 27 Sep 2018 14:37:06 +0200 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH 4.18 74/88] drm/atomic: Use drm_drv_uses_atomic_modeset() for debugfs creation |
| |
On Thu, Sep 27, 2018 at 12:43:33PM +0200, Holger Hoffstätte wrote: > On 09/27/18 11:03, Greg Kroah-Hartman wrote: > > 4.18-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Lyude Paul <lyude@redhat.com> > > > > commit 3c499ea0c662e2f38aafbd4f516b08aab8cfa0e5 upstream. > > > > As pointed out by Daniel Vetter, we should be usinng > > drm_drv_uses_atomic_modeset() for determining whether or not we want to > > make the debugfs nodes for atomic instead of checking DRIVER_ATOMIC, as > > the former isn't an accurate representation of whether or not the driver > > is actually using atomic modesetting internally (even though it might > > not be exposing atomic capabilities). > > > > Signed-off-by: Lyude Paul <lyude@redhat.com> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch> > > Cc: stable@vger.kernel.org > > Reviewed-by: Sean Paul <seanpaul@chromium.org> > > Link: https://patchwork.freedesktop.org/patch/msgid/20180917173733.21293-1-lyude@redhat.com > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > > This patch breaks switching the console to high resolution during boot on my > workstation with a Radeon card; it worked fine with 4.18.10 and reverting it > fixes the problem:
Is 4.19-rc5 also a problem?
thanks,
greg k-h
| |