✓ CI.checkpatch: success for drm/{i915,xe}: Convert fbdev to DRM client

[Patchwork]

== Series Details ==

Series: drm/{i915,xe}: Convert fbdev to DRM client
URL   : https://patchwork.freedesktop.org/series/132193/
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
10b531c2aeb176a1a539b4a77216232f97719cec
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 01c9492f7ed73a8afae53249d54b9c6feae1ed46
Author: Thomas Zimmermann <tzimmermann at suse.de>
Date:   Tue Apr 9 10:04:28 2024 +0200

    drm/{i915, xe}: 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. Do the same for xe.
    
    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().
    
    v8:
    - setup client in intel_display_driver_register (Jouni)
    - mention xe in commit message
    
    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 at suse.de>
+ /mt/dim checkpatch 2417474ba0be0f6b5838349e9f44419f530511e4 drm-intel
acf941fcd2ed drm/client: Export drm_client_dev_unregister()
c0c0bb19ef87 drm/i915: Move fbdev functions
83819ef2990c drm/i915: Initialize fbdev DRM client with callback functions
029e9437d1a2 drm/{i915,xe}: Unregister in-kernel clients
1a17e9bb2e4c drm/{i915,xe}: Implement fbdev client callbacks
01c9492f7ed7 drm/{i915, xe}: Implement fbdev emulation as in-kernel client