✓ CI.checkpatch: success for drm/i915: Convert fbdev to DRM client

From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for drm/i915: Convert fbdev to DRM client
Date: Fri, 01 Mar 2024 13:50:16 -0000	[thread overview]
Message-ID: <170930101693.436087.988008782431397123@8e613ede5ea5> (raw)
In-Reply-To: <20240301134448.31289-1-tzimmermann@suse.de>

== Series Details ==

Series: drm/i915: Convert fbdev to DRM client
URL   : https://patchwork.freedesktop.org/series/130615/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
4dc7d0cc630cdd9ac56065b1a22afc329345a519
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 7e6aba38974b8cefad4b9a665173d065dd7708d5
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Fri Mar 1 14:42:59 2024 +0100

    drm/i915: Implement fbdev emulation as in-kernel client
    
    Replace all code that initializes or releases fbdev emulation
    throughout the driver. Instead initialize the fbdev client by a
    single call to intel_fbdev_setup() after i915 has registered its
    DRM device. Just like similar code in other drivers, i915 fbdev
    emulation now acts like a regular DRM client.
    
    The fbdev client setup consists of the initial preparation and the
    hot-plugging of the display. The latter creates the fbdev device
    and sets up the fbdev framebuffer. The setup performs display
    hot-plugging once. If no display can be detected, DRM probe helpers
    re-run the detection on each hotplug event.
    
    A call to drm_client_dev_unregister() releases all in-kernel clients
    automatically. No further action is required within i915. If the fbdev
    framebuffer has been fully set up, struct fb_ops.fb_destroy implements
    the release. For partially initialized emulation, the fbdev client
    reverts the initial setup. Do the same for xe and remove its call to
    intel_fbdev_fini().
    
    v7:
            * update xe driver
            * reword commit message
    v6:
            * use 'i915' for i915 device (Jouni)
            * remove unnecessary code for non-atomic mode setting
              (Jouni, Ville)
            * fix function name in commit message (Jouni)
    v3:
            * as before, silently ignore devices without displays
    v2:
            * let drm_client_register() handle initial hotplug
            * fix driver name in error message (Jani)
            * fix non-fbdev build (kernel test robot)
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
+ /mt/dim checkpatch 320f2374b2d52629a6a52c6c3059f02efd73c0a5 drm-intel
5bef5a2f1296 drm/client: Export drm_client_dev_unregister()
16daeba12ad5 drm/i915: Unregister in-kernel clients
2cd05a1754a7 drm/i915: Move fbdev functions
ba6a463f332f drm/i915: Initialize fbdev DRM client with callback functions
bfb2c3151675 drm/i915: Implement fbdev client callbacks
7e6aba38974b drm/i915: Implement fbdev emulation as in-kernel client