Linux DRI Development

• Date Index

• [PATCH] drm: dw_hdmi: Remove non-standard "gpr" property, Fabio Estevam
• Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
  • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
    • Re: Question regarding clocks in the DW-HDMI DT bindings, Vladimir Zapolskiy
      • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
      • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
        • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
          • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
        • Re: Question regarding clocks in the DW-HDMI DT bindings, Andy Yan
          • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
            • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
              • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
              • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
                • Re: Question regarding clocks in the DW-HDMI DT bindings, Vladimir Zapolskiy
                  • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
            • Re: Question regarding clocks in the DW-HDMI DT bindings, Michael Turquette
              • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
                • Re: Question regarding clocks in the DW-HDMI DT bindings, Michael Turquette
                  • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
      • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
        • Re: Question regarding clocks in the DW-HDMI DT bindings, Vladimir Zapolskiy
          • Re: Question regarding clocks in the DW-HDMI DT bindings, Fabio Estevam
            • Re: Question regarding clocks in the DW-HDMI DT bindings, Vladimir Zapolskiy
  • Re: Question regarding clocks in the DW-HDMI DT bindings, Philipp Zabel
    • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
      • Re: Question regarding clocks in the DW-HDMI DT bindings, Philipp Zabel
        • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
          • Re: Question regarding clocks in the DW-HDMI DT bindings, Andy Yan
            • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
              • Re: Question regarding clocks in the DW-HDMI DT bindings, Jose Abreu
                • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
                  • Re: Question regarding clocks in the DW-HDMI DT bindings, Jose Abreu
                    • Re: Question regarding clocks in the DW-HDMI DT bindings, Laurent Pinchart
                      • Re: Question regarding clocks in the DW-HDMI DT bindings, Jose Abreu
• [PATCH] drm/atomic: Constify drm_atomic_crtc_needs_modeset(), ville . syrjala
  • Re: [PATCH] drm/atomic: Constify drm_atomic_crtc_needs_modeset(), Jani Nikula
    • Re: [PATCH] drm/atomic: Constify drm_atomic_crtc_needs_modeset(), Ville Syrjälä
• [PATCH] drm/hisilicon/hibmc: mark PM functions __maybe_unused, Arnd Bergmann
  • Re: [PATCH] drm/hisilicon/hibmc: mark PM functions __maybe_unused, Daniel Vetter
• TDA998x crash on HDLCD probe failure, Robin Murphy
  • Re: TDA998x crash on HDLCD probe failure, Russell King - ARM Linux
    • Re: TDA998x crash on HDLCD probe failure, Robin Murphy
      • Re: TDA998x crash on HDLCD probe failure, Robin Murphy
        • Re: TDA998x crash on HDLCD probe failure, Liviu Dudau
• [patch] drm/hisilicon/hibmc: Checking for NULL instead of IS_ERR(), Dan Carpenter
  • Re: [patch] drm/hisilicon/hibmc: Checking for NULL instead of IS_ERR(), Daniel Vetter
• drm-intel split-up and new dim script, Daniel Vetter
  • Re: drm-intel split-up and new dim script, Jani Nikula
  • Re: drm-intel split-up and new dim script, Daniel Vetter
  • Re: drm-intel split-up and new dim script, Daniel Vetter
• [PATCH] drm/atmel-hlcdc: clock fixes, use drm component API to access tda998x driver, hupster
• [PATCH] ARM: dts: da850: enable the memctrl and mstpri nodes per board, Bartosz Golaszewski
  • Re: [PATCH] ARM: dts: da850: enable the memctrl and mstpri nodes per board, Sekhar Nori
• [PATCH libdrm v4 0/2] etna_pipe_wait_ns(..), Christian Gmeiner
  • [PATCH libdrm v4 1/2] etnaviv: change get_abs_timeout(..) to use ns., Christian Gmeiner
  • [PATCH libdrm v4 2/2] etnaviv: add etna_pipe_wait_ns(..), Christian Gmeiner
  • Re: [PATCH libdrm v4 0/2] etna_pipe_wait_ns(..), Emil Velikov
• [PATCH] drm/exynos/gsc: fix the hardware limitations, Hoegeun Kwon
  • Re: [PATCH] drm/exynos/gsc: fix the hardware limitations, Inki Dae
• [GIT PULL] arm/hdlcd fixes for v4.9-rc7, Liviu Dudau
• [PATCH] drm: Add support for extracting sync signal drive edge from videomode, Peter Ujfalusi
• [PATCH] drm/doc: Fix links in drm_property.c, Daniel Vetter
  • Re: [PATCH] drm/doc: Fix links in drm_property.c, Sean Paul
• [PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs, Chris Wilson
  • [PATCH 2/3] drm: Pull together probe + setup for drm_fb_helper, Chris Wilson
    • Re: [PATCH 2/3] drm: Pull together probe + setup for drm_fb_helper, Daniel Vetter
  • [PATCH 3/3] drm: Protect fb_helper list manipulation with a mutex, Chris Wilson
    • Re: [PATCH 3/3] drm: Protect fb_helper list manipulation with a mutex, Daniel Vetter
      • Re: [PATCH 3/3] drm: Protect fb_helper list manipulation with a mutex, Chris Wilson
        • Re: [PATCH 3/3] drm: Protect fb_helper list manipulation with a mutex, Daniel Vetter
  • Re: [PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs, Jani Nikula
  • Re: [PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs, Daniel Vetter
    • Re: [PATCH 1/3] drm: Hold mode_config.lock to prevent hotplug whilst setting up crtcs, Chris Wilson
• [RFC PATCH 0/3] staging: remove fbdev drivers, Tomi Valkeinen
  • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Greg Kroah-Hartman
    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Tomi Valkeinen
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Greg Kroah-Hartman
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Thomas Petazzoni
        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Andy Shevchenko
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Sudip Mukherjee
  • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Tomi Valkeinen
  • [RFC PATCH 2/3] staging: remove sm750fb, Tomi Valkeinen
  • [RFC PATCH 3/3] staging: remove fbtft, Tomi Valkeinen
    • Re: [RFC PATCH 3/3] staging: remove fbtft, Noralf Trønnes
      • Re: [RFC PATCH 3/3] staging: remove fbtft, Tomi Valkeinen
    • Re: [RFC PATCH 3/3] staging: remove fbtft, Drew Fustini
  • [RFC PATCH 1/3] staging: remove xgifb, Tomi Valkeinen
  • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Tomi Valkeinen
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Gerd Hoffmann
    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
            • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Jani Nikula
            • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Thomas Petazzoni
              • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
                • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                  • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                    • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                            • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                              • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                                • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Michel Dänzer
                        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
                          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Lucas Stach
                          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                            • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, David Herrmann
                              • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
                              • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
                  • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Daniel Vetter
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
        • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Dave Airlie
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Geert Uytterhoeven
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Benjamin Herrenschmidt
          • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Gerd Hoffmann
      • Re: [RFC PATCH 0/3] staging: remove fbdev drivers, Laurent Pinchart
• [PATCH 1/5] drm: Define drm_mm_for_each_node_in_range(), Chris Wilson
  • [PATCH 2/5] drm: Check against color expansion in drm_mm_reserve_node(), Chris Wilson
    • Re: [PATCH 2/5] drm: Check against color expansion in drm_mm_reserve_node(), Daniel Vetter
    • Re: [PATCH 2/5] drm: Check against color expansion in drm_mm_reserve_node(), Daniel Vetter
• [PATCH] MAINTAINERS: Add link to drm-misc documentation, Daniel Vetter
• [PATCH v4 0/2] da8xx: fix section mismatch in new drivers, Bartosz Golaszewski
  • [PATCH v4 2/2] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • [PATCH v4 1/2] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • Re: [PATCH v4 0/2] da8xx: fix section mismatch in new drivers, Sekhar Nori
• [PATCH v3 0/3] da8xx: fix section mismatch in new drivers, Bartosz Golaszewski
  • [PATCH v3 2/3] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • [PATCH v3 3/3] bus: da8xx-mstpri: fix a typo, Bartosz Golaszewski
  • [PATCH v3 1/3] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
    • Re: [PATCH v3 1/3] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name(), Sekhar Nori
• [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Nicolai Hähnle
  • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Peter Zijlstra
    • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Daniel Vetter
      • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Daniel Vetter
        • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Maarten Lankhorst
  • [PATCH 2/4] locking/ww_mutex: Remove redundant wakeups in ww_mutex_set_context_slowpath, Nicolai Hähnle
  • [PATCH 3/4] locking/Documentation: fix a typo, Nicolai Hähnle
  • [PATCH 4/4] locking/ww_mutex: Fix a comment typo, Nicolai Hähnle
  • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Daniel Vetter
  • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Peter Zijlstra
    • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Daniel Vetter
      • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Peter Zijlstra
      • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Nicolai Hähnle
        • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Peter Zijlstra
          • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Daniel Vetter
            • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Peter Zijlstra
              • Re: [PATCH 1/4] locking/ww_mutex: Fix a deadlock affecting ww_mutexes, Nicolai Hähnle
• [PATCH] drm-misc: Flesh out the documentation a bit, Daniel Vetter
• [Bug 98834] Screen not refreshed after 1106b2f773ad0611c729b27f4c192a26b43ef1e7, bugzilla-daemon
  • [Bug 98834] Screen not refreshed after 1106b2f773ad0611c729b27f4c192a26b43ef1e7, bugzilla-daemon
• [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Christian Gmeiner
  • [PATCH libdrm v3 1/4] etnaviv: add etna_pipe_wait_ns(..), Christian Gmeiner
  • [PATCH libdrm v3 3/4] etnaviv: use get_abs_timeout_ns(..) internally, Christian Gmeiner
  • [PATCH libdrm v3 2/4] etnaviv: simplify etna_pipe_wait(..), Christian Gmeiner
  • [PATCH libdrm v3 4/4] etnaviv: drop get_abs_timeout(..), Christian Gmeiner
  • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Emil Velikov
    • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Rob Clark
      • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Emil Velikov
        • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Rob Clark
          • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Daniel Vetter
            • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Christian Gmeiner
    • Re: [PATCH libdrm v3 0/4] etna_pipe_wait_ns(..), Christian Gmeiner
• [PATCH] drm/nouveau/kms/nv50: Fix atomic pageflip events., Mario Kleiner
• [PATCH RFC] drm: Add a new connector atomic property for link status, Manasi Navare
  • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
    • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Daniel Vetter
      • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
        • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Jani Nikula
          • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
            • Re: [Intel-gfx] [PATCH RFC] drm: Add a new connector atomic property for link status, Ville Syrjälä
              • Re: [Intel-gfx] [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
            • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Jani Nikula
              • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Daniel Vetter
              • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
      • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Manasi Navare
        • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
          • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Sean Paul
            • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Manasi Navare
  • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Daniel Vetter
    • Re: [PATCH RFC] drm: Add a new connector atomic property for link status, Manasi Navare
  • [PATCH RFC v2] drm: Add a new connector atomic property for link status, Manasi Navare
    • [PATCH RFC v3] drm: Add a new connector atomic property for link status, Manasi Navare
      • Re: [PATCH RFC v3] drm: Add a new connector atomic property for link status, Daniel Vetter
        • Re: [PATCH RFC v3] drm: Add a new connector atomic property for link status, Manasi Navare
        • Re: [PATCH RFC v3] drm: Add a new connector atomic property for link status, Manasi Navare
          • Re: [PATCH RFC v3] drm: Add a new connector atomic property for link status, Daniel Vetter
            • Re: [PATCH RFC v3] drm: Add a new connector atomic property for link status, Manasi Navare
• [PATCH libdrm v2 0/3] etna_pipe_wait_ns(..), Christian Gmeiner
  • [PATCH libdrm v2 2/3] etnaviv: simplify etna_pipe_wait(..), Christian Gmeiner
  • [PATCH libdrm v2 1/3] etnaviv: add etna_pipe_wait_ns(..), Christian Gmeiner
  • [PATCH libdrm v2 3/3] etnaviv: s/get_abs_timeout_ns/get_abs_timeout, Christian Gmeiner
• [PATCH libdrm] etnaviv: add etna_pipe_wait2(..), Christian Gmeiner
  • Re: [PATCH libdrm] etnaviv: add etna_pipe_wait2(..), Christian Gmeiner
• [PATCH 0/5] Add Automation support for DP compliance testing, Manasi Navare
  • [PATCH 3/5] Add support for forcing 6 bpc on DP pipes., Manasi Navare
    • Re: [PATCH 3/5] Add support for forcing 6 bpc on DP pipes., Jani Nikula
  • [PATCH 2/5] drm/i915: Fixes to support DP Compliance EDID tests, Manasi Navare
  • [PATCH 1/5] drm/i915: Add support for DP link training compliance, Manasi Navare
    • Re: [PATCH 1/5] drm/i915: Add support for DP link training compliance, Jani Nikula
      • Re: [PATCH 1/5] drm/i915: Add support for DP link training compliance, Manasi Navare
        • Re: [PATCH 1/5] drm/i915: Add support for DP link training compliance, Jani Nikula
  • [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Manasi Navare
    • Re: [Intel-gfx] [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Daniel Vetter
    • Re: [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Jani Nikula
      • Re: [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Ville Syrjälä
        • Re: [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Jani Nikula
          • Re: [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Daniel Vetter
            • Re: [PATCH 5/5] drm/i915: Add support for DP Video pattern compliance tests, Ville Syrjälä
  • [PATCH 4/5] drm: Add definitions for DP compliance Video pattern tests, Manasi Navare
    • Re: [PATCH 4/5] drm: Add definitions for DP compliance Video pattern tests, Jani Nikula
• [PATCH 0/3] drm/rockchip: Add CDN DP driver, Sean Paul
  • [PATCH v16 1/3] drm/rockchip: cdn-dp: add cdn DP support for rk3399, Sean Paul
  • [PATCH 2/3] drm/rockchip: cdn-dp: Load firmware if no monitor connected, Sean Paul
  • [PATCH 3/3] drm/rockchip: cdn-dp: Do not run worker while suspended, Sean Paul
• [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
  • [Bug 98821] [amdgpu][bisected][polaris] "drm/amdgpu: refine uvd 6.0 clock gate feature" sets MCLK on highest state, bugzilla-daemon
• [drm-intel:drm-intel-next-queued 6/11] ERROR: "__udivdi3" [drivers/gpu/drm/i915/i915.ko] undefined!, kbuild test robot
• [PATCH v3 00/11] drm/tilcdc: LCDC Revision 1 related fixes, Jyri Sarha
  • [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
    • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Tomi Valkeinen
      • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
        • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Tomi Valkeinen
          • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
            • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Tomi Valkeinen
              • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
                • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Tomi Valkeinen
                  • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
                    • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Tomi Valkeinen
                      • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Jyri Sarha
                        • Re: [PATCH v3 02/11] drm/tilcdc: implement palette loading for rev1, Daniel Vetter
  • [PATCH v3 01/11] drm/tilcdc: Enable sync lost error and recovery handling for rev 1 LCDC, Jyri Sarha
    • Re: [PATCH v3 01/11] drm/tilcdc: Enable sync lost error and recovery handling for rev 1 LCDC, Bartosz Golaszewski
  • [PATCH v3 05/11] drm/tilcdc: Fix load mode bit-field setting in tilcdc_crtc_enable(), Jyri Sarha
  • [PATCH v3 04/11] drm/tilcdc: Add tilcdc_write_mask() to tilcdc_regs.h, Jyri Sarha
  • [PATCH v3 11/11] drm/tilcdc: Enable frame done irq and functionality for LCDC rev 1, Jyri Sarha
    • Re: [PATCH v3 11/11] drm/tilcdc: Enable frame done irq and functionality for LCDC rev 1, Bartosz Golaszewski
  • [PATCH v3 10/11] drm/tilcdc: Load palette at the end of mode_set_nofb(), Jyri Sarha
  • [PATCH v3 07/11] drm/tilcdc: Add timeout wait for palette loading to complete, Jyri Sarha
    • Re: [PATCH v3 07/11] drm/tilcdc: Add timeout wait for palette loading to complete, Tomi Valkeinen
  • [PATCH v3 09/11] drm/tilcdc: Use complete_all() to indicate completed palette loading, Jyri Sarha
  • [PATCH v3 06/11] drm/tilcdc: Enable palette loading for revision 2 LCDC too, Jyri Sarha
    • Re: [PATCH v3 06/11] drm/tilcdc: Enable palette loading for revision 2 LCDC too, Bartosz Golaszewski
    • Re: [PATCH v3 06/11] drm/tilcdc: Enable palette loading for revision 2 LCDC too, Tomi Valkeinen
      • Re: [PATCH v3 06/11] drm/tilcdc: Enable palette loading for revision 2 LCDC too, Jyri Sarha
  • [PATCH v3 08/11] drm/tilcdc: Call reset() before loading the palette, Jyri Sarha
  • [PATCH v3 03/11] drm/tilcdc: Fix tilcdc_crtc_create() return value handling, Jyri Sarha
    • Re: [PATCH v3 03/11] drm/tilcdc: Fix tilcdc_crtc_create() return value handling, Tomi Valkeinen
• [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
  • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Ville Syrjälä
    • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Rob Clark
      • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Ville Syrjälä
        • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Rob Clark
          • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Ville Syrjälä
            • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Sean Paul
              • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
                • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Rob Clark
          • [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
            • Re: [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Jani Nikula
              • Re: [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
                • Re: [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Daniel Vetter
                  • Re: [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Jani Nikula
                    • Re: [PATCH v2] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
      • Re: [PATCH] drm: check for NULL parameter in exported drm_get_format_name() function., Liviu Dudau
• [PATCH 0/3] drm/msm cleanups, Jordan Crouse
  • [PATCH 1/3] drm/msm: gpu: Cut down the list of "generic" registers to the ones we use, Jordan Crouse
  • [PATCH 2/3] drm/msm: gpu: Return error on hw_init failure, Jordan Crouse
  • [PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions, Jordan Crouse
    • Re: [PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions, Stephen Boyd
      • Re: [PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions, Rob Clark
        • Re: [PATCH 3/3] drm/msm: gpu Add new gpu register read/write functions, Stephen Boyd
• [drm-intel:drm-intel-next-queued 6/11] undefined reference to `__udivdi3', kbuild test robot
• [PATCH v4 0/4] drm/tilcdc: Add bridge support and sync-lost flood recovery, Jyri Sarha
  • [PATCH v4 2/4] dt-bindings: Move "ti, tfp410.txt" from display/ti to display/bridge, Jyri Sarha
    • Re: [PATCH v4 2/4] dt-bindings: Move "ti, tfp410.txt" from display/ti to display/bridge, Rob Herring
  • [PATCH v4 1/4] drm/tilcdc: Recover from sync lost error flood by resetting the LCDC, Jyri Sarha
  • [PATCH v4 4/4] drm/tilcdc: Add drm bridge support for attaching drm bridge drivers, Jyri Sarha
  • [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver, Jyri Sarha
    • Re: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver, Jyri Sarha
      • Re: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver, Jani Nikula
    • Re: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver, Rob Herring
• [PATCH] vgaarb: use valid dev pointer in vgaarb_info(), Arnd Bergmann
  • Re: [PATCH] vgaarb: use valid dev pointer in vgaarb_info(), Daniel Vetter
• [PATCH v2 0/2] da8xx: fix section mismatch in new drivers, Bartosz Golaszewski
  • [PATCH v2 1/2] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • [PATCH v2 2/2] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
• [PATCH] drm/etnaviv: implement dma-buf mmap, Lucas Stach
• [PATCH 0/3] ARM: da8xx: fix section mismatch in new drivers, Bartosz Golaszewski
  • [PATCH 2/3] bus: da8xx-mstpri: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • [PATCH 3/3] memory: da8xx-ddrctl: drop the call to of_flat_dt_get_machine_name(), Bartosz Golaszewski
  • [PATCH 1/3] of: base: add support to get machine compatible string, Bartosz Golaszewski
    • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
      • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Bartosz Golaszewski
        • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Bartosz Golaszewski
        • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
          • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sekhar Nori
      • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sekhar Nori
        • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
          • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sekhar Nori
            • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
              • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sekhar Nori
                • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
                  • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sekhar Nori
                    • Re: [PATCH 1/3] of: base: add support to get machine compatible string, Sudeep Holla
• [PATCH] drm: flip cirrus driver status to "obsolete"., Gerd Hoffmann
• [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Gerd Hoffmann
  • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Thomas Huth
    • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Eric Blake
      • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Paolo Bonzini
        • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Eric Blake
          • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Gerd Hoffmann
            • Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu), Thomas Huth
• [PATCH] ARM: dts: da850: specify max width for display node, Bartosz Golaszewski
  • Re: [PATCH] ARM: dts: da850: specify max width for display node, Tomi Valkeinen
    • Re: [PATCH] ARM: dts: da850: specify max width for display node, Bartosz Golaszewski
• [PATCH] drm: tilcdc: fix a DT property parsing, Bartosz Golaszewski
• [PATCH] drm/radeon: Ensure vblank interrupt is enabled on DPMS transition to on, Michel Dänzer
  • Re: [PATCH] drm/radeon: Ensure vblank interrupt is enabled on DPMS transition to on, Daniel Vetter
  • Re: [PATCH] drm/radeon: Ensure vblank interrupt is enabled on DPMS transition to on, Alex Deucher
• [PATCH v5 0/2] drm/panel: simple: add support for Sharp LQ150X1LG11 panels, Peter Rosin
  • [PATCH v5 1/2] dt-bindings: display: Add Sharp LQ150X1LG11 panel binding, Peter Rosin
    • Re: [PATCH v5 1/2] dt-bindings: display: Add Sharp LQ150X1LG11 panel binding, Rob Herring
  • [PATCH v5 2/2] drm/panel: simple: add support for Sharp LQ150X1LG11 panels, Peter Rosin
• [PATCH] drm/arm: hdlcd: fix plane base address calculation, Russell King
• [RFC][PATCH 0/3] adv7511 EDID probing improvements, John Stultz
  • [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
    • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, Laurent Pinchart
      • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
        • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, Laurent Pinchart
      • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
        • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, Laurent Pinchart
          • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
          • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
            • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, Archit Taneja
              • Re: [RFC][PATCH 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally, John Stultz
  • [RFC][PATCH 3/3] drm/bridge: adv7511: Enable HPD interrupts to support hotplug and improve monitor detection, John Stultz
    • Re: [RFC][PATCH 3/3] drm/bridge: adv7511: Enable HPD interrupts to support hotplug and improve monitor detection, Laurent Pinchart
  • [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, John Stultz
    • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, Laurent Pinchart
      • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, John Stultz
        • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, John Stultz
          • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, Laurent Pinchart
            • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, John Stultz
            • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, Daniel Vetter
              • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, Laurent Pinchart
                • Re: [RFC][PATCH 2/3] drm/bridge: adv7511: Add 200ms delay on power-on, Daniel Vetter
• [PATCH v2] drm/fences: add DOC: for explicit fencing, Gustavo Padovan
  • Re: [PATCH v2] drm/fences: add DOC: for explicit fencing, Daniel Vetter
• [Bug 188321] New: i915: black screen after disconnecting HDMI monitor, bugzilla-daemon
  • [Bug 188321] i915: black screen after disconnecting HDMI monitor, bugzilla-daemon
• Enabling peer to peer device transactions for PCIe devices, Deucher, Alexander
  • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
    • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
      • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
        • Re: Enabling peer to peer device transactions for PCIe devices, Daniel Vetter
          • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
          • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
            • Re: Enabling peer to peer device transactions for PCIe devices, Daniel Vetter
              • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                • Re: Enabling peer to peer device transactions for PCIe devices, Sagalovitch, Serguei
                • Re: Enabling peer to peer device transactions for PCIe devices, Daniel Vetter
                  • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                    • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                  • Re: Enabling peer to peer device transactions for PCIe devices, Dave Hansen
              • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
      • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
        • Re: Enabling peer to peer device transactions for PCIe devices, Bart Van Assche
          • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
            • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
              • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
          • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
          • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
            • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
              • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                  • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                      • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                          • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                            • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                              • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                            • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                              • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                                • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                  • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                    • Re: Enabling peer to peer device transactions for PCIe devices, Felix Kuehling
                                      • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                      • Re: Enabling peer to peer device transactions for PCIe devices, Sagalovitch, Serguei
                        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                      • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                          • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                            • Re: Enabling peer to peer device transactions for PCIe devices, Christoph Hellwig
                              • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                            • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                          • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                            • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                              • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                  • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                • Re: Enabling peer to peer device transactions for PCIe devices, Alex Deucher
                            • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                              • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                                • Re: Enabling peer to peer device transactions for PCIe devices, Felix Kuehling
                                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                              • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                                  • Re: Enabling peer to peer device transactions for PCIe devices, zhoucm1
                                • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                  • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                  • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                      • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                        • RE: Enabling peer to peer device transactions for PCIe devices, Deucher, Alexander
                                        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                          • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                            • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                          • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                            • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                              • Re: Enabling peer to peer device transactions for PCIe devices, Stephen Bates
                                              • Re: Enabling peer to peer device transactions for PCIe devices, Stephen Bates
                                                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                  • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Christoph Hellwig
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Stephen Bates
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Christoph Hellwig
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                                    • Re: Enabling peer to peer device transactions for PCIe devices, Dan Williams
                                          • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
                                  • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                    • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                      • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                                        • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                                          • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                              • Re: Enabling peer to peer device transactions for PCIe devices, Haggai Eran
  • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
    • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
      • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
          • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
            • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
              • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                  • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
                    • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
                      • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
                        • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                          • RE: Enabling peer to peer device transactions for PCIe devices, Deucher, Alexander
                          • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                            • Re: Enabling peer to peer device transactions for PCIe devices, Stephen Bates
                              • Re: Enabling peer to peer device transactions for PCIe devices, Jerome Glisse
                                • Re: Enabling peer to peer device transactions for PCIe devices, Jason Gunthorpe
                                • Re: Enabling peer to peer device transactions for PCIe devices, Christian König
                              • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
                  • Re: Enabling peer to peer device transactions for PCIe devices, Serguei Sagalovitch
      • Re: Enabling peer to peer device transactions for PCIe devices, Henrique Almeida
  • Re: Enabling peer to peer device transactions for PCIe devices, Ludwig Petrosyan
    • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
      • Re: Enabling peer to peer device transactions for PCIe devices, Petrosyan, Ludwig
        • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
        • RE: Enabling peer to peer device transactions for PCIe devices, David Laight
          • Re: Enabling peer to peer device transactions for PCIe devices, Logan Gunthorpe
            • Re: Enabling peer to peer device transactions for PCIe devices, Petrosyan, Ludwig
              • RE: Enabling peer to peer device transactions for PCIe devices, David Laight
                • Re: Enabling peer to peer device transactions for PCIe devices, Petrosyan, Ludwig
• RfC: MAINTAINERS update for qemu drm drivers., Gerd Hoffmann
  • Re: RfC: MAINTAINERS update for qemu drm drivers., Daniel Vetter
    • Re: RfC: MAINTAINERS update for qemu drm drivers., Gerd Hoffmann
• [PULL] drm-qemu for 4.10, Gerd Hoffmann
• [Bug 188271] New: IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
  • [Bug 188271] IOMMU DMAR fault with NVIDIA CUDA peer to peer, bugzilla-daemon
• [PATCH] drm: tilcdc: reduce max_width for revision 1, Bartosz Golaszewski
  • [PATCH] drm: tilcdc: reduce max_width for revision 1, Bartosz Golaszewski
    • Re: [PATCH] drm: tilcdc: reduce max_width for revision 1, Jyri Sarha
      • Re: [PATCH] drm: tilcdc: reduce max_width for revision 1, Bartosz Golaszewski
• [PATCH 1/2] drm/nouveau: Rename acpi_work to hpd_work, Hans de Goede
  • [PATCH 2/2] drm/nouveau: Queue hpd_work on (runtime) resume, Hans de Goede
    • Re: [PATCH 2/2] drm/nouveau: Queue hpd_work on (runtime) resume, Mario Kleiner
      • Re: [PATCH 2/2] drm/nouveau: Queue hpd_work on (runtime) resume, Hans de Goede
• [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Daniel Vetter
  • [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Daniel Vetter
    • Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Liviu Dudau
  • [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Daniel Vetter
    • Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Gustavo Padovan
      • Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Russell King - ARM Linux
    • Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Daniel Vetter
  • Re: [PATCH] drm/atomic: Unconfuse the old_state mess in commmit_tail, Russell King - ARM Linux
• [PATCH] drm/fences: add DOC: for explicit fencing, Gustavo Padovan
  • Re: [PATCH] drm/fences: add DOC: for explicit fencing, Daniel Vetter
• [PATCH libdrm] libdrm: random typo fixes, Grazvydas Ignotas
  • [PATCH libdrm] tests: kms: fix shadowed declaration warning, Grazvydas Ignotas
  • Re: [PATCH libdrm] libdrm: random typo fixes, Alex Deucher
    • Re: [PATCH libdrm] libdrm: random typo fixes, Emil Velikov
• [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
  • [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
  • [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
  • [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
  • [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
  • [Bug 98795] Rendering regression in radeonsi running mad max, bugzilla-daemon
• [PATCH v6 0/5] drm: sun8i: Add DE2 HDMI video support, Jean-Francois Moine
  • [PATCH v6 5/5] ARM: dts: sun8i-h3: Add HDMI video to the Orange PI 2, Jean-Francois Moine
  • [PATCH v6 1/5] drm: sun8i: Add a basic DRM driver for Allwinner DE2, Jean-Francois Moine
    • Re: [PATCH v6 1/5] drm: sun8i: Add a basic DRM driver for Allwinner DE2, Rob Herring
  • [PATCH v6 4/5] ARM: dts: sun8i-h3: Add HDMI video to the Banana Pi M2+, Jean-Francois Moine
  • [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Jean-Francois Moine
    • Re: [linux-sunxi] [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Icenowy Zheng
      • Re: [linux-sunxi] [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Jean-François Moine
    • Re: [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Icenowy Zheng
      • Re: [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Jean-Francois Moine
        • Re: [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Icenowy Zheng
        • Re: [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Maxime Ripard
        • Re: [PATCH v6 3/5] ARM: dts: sun8i-h3: add HDMI video nodes, Jernej Skrabec
  • [PATCH v6 2/5] drm: sun8i: add HDMI video support to A83T and H3, Jean-Francois Moine
    • Re: [PATCH v6 2/5] drm: sun8i: add HDMI video support to A83T and H3, Rob Herring
  • Re: [linux-sunxi] [PATCH v6 0/5] drm: sun8i: Add DE2 HDMI video support, Ondřej Jirman
    • Re: [linux-sunxi] [PATCH v6 0/5] drm: sun8i: Add DE2 HDMI video support, Jean-Francois Moine
      • Re: [linux-sunxi] [PATCH v6 0/5] drm: sun8i: Add DE2 HDMI video support, Ondřej Jirman
• [Bug 98778] 3D is not working., bugzilla-daemon
  • <Possible follow-ups>
  • [Bug 98778] 3D is not working., bugzilla-daemon
  • [Bug 98778] 3D is not working., bugzilla-daemon
• [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
  • Re: [BUG] hdlcd gets confused about base address, Daniel Vetter
  • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
    • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
      • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
        • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
          • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
            • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
              • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
                • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                  • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
                    • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                      • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
                        • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                      • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                        • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
              • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
                  • Re: [BUG] hdlcd gets confused about base address, Daniel Vetter
  • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
    • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
      • Re: [BUG] hdlcd gets confused about base address, Ville Syrjälä
        • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
          • Re: [BUG] hdlcd gets confused about base address, Ville Syrjälä
            • Re: [BUG] hdlcd gets confused about base address, Daniel Vetter
        • Re: [BUG] hdlcd gets confused about base address, Liviu Dudau
          • Re: [BUG] hdlcd gets confused about base address, Ville Syrjälä
            • [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Liviu Dudau
              • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Russell King - ARM Linux
                • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Liviu Dudau
                  • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Russell King - ARM Linux
                    • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Liviu Dudau
                      • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Russell King - ARM Linux
                        • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Liviu Dudau
                        • Re: [PATCH v2] drm: hdlcd: Fix the calculation of the scanout start address, Jani Nikula
                • [PATCH 2/3] drm/arm: hdlcd: fix plane base address calculation, Russell King
                  • Re: [PATCH 2/3] drm/arm: hdlcd: fix plane base address calculation, Liviu Dudau
                • [PATCH 3/3] drm/arm: hdlcd: check for rotation, Russell King
                  • Re: [PATCH 3/3] drm/arm: hdlcd: check for rotation, Ville Syrjälä
                    • Re: [PATCH 3/3] drm/arm: hdlcd: check for rotation, Liviu Dudau
                • [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Russell King
                  • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Liviu Dudau
                    • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Russell King - ARM Linux
                      • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Liviu Dudau
                        • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Russell King - ARM Linux
                          • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Liviu Dudau
                            • Re: [PATCH 1/3] drm/arm: hdlcd: properly validate plane state, Russell King - ARM Linux
      • Re: [BUG] hdlcd gets confused about base address, Russell King - ARM Linux
• [Resend PATCH] drm/mediatek: fix null pointer dereference, Matthias Brugger
• [PATCH] drm/panel: simple: add 8bit-bps for Sharp lq123p1jx31, zain wang
  • Re: [PATCH] drm/panel: simple: add 8bit-bps for Sharp lq123p1jx31, Thierry Reding
• [PATCH] drm: mediatek: use ERR_CAST inlined function, Geliang Tang
• [PATCH] drm/sun4i: Fix a return value in case of error, Christophe JAILLET
  • Re: [PATCH] drm/sun4i: Fix a return value in case of error, Maxime Ripard
• [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
  • [Bug 98785] Talos Principle causes GPU faults when rendering main menu animation, bugzilla-daemon
• [Bug 98784] Talos Principle rendering flickering garbage on start instead of Croteam logo, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
  • [Bug 98784] Talos Principle rendering flickering garbage on start instead of its logo and loading squares, bugzilla-daemon
• [Bug 98777] GPU lockup in Guns of Icarus Online, bugzilla-daemon
  • [Bug 98777] GPU lockup in Guns of Icarus Online, bugzilla-daemon
  • [Bug 98777] GPU lockup in Guns of Icarus Online, bugzilla-daemon
  • [Bug 98777] GPU lockup in Guns of Icarus Online, bugzilla-daemon
• [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
  • [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
  • [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
  • [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
  • [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
  • [Bug 98776] [regression] Rendering glitches in Life Is Strange, bugzilla-daemon
• [PATCH v2 0/9] R-Car DU: Use drm bridge API, Laurent Pinchart
  • [PATCH v2 1/9] drm: bridge: Add LVDS encoder DT bindings, Laurent Pinchart
  • [PATCH v2 3/9] drm: bridge: vga-dac: Add adi, adv7123 compatible string, Laurent Pinchart
  • [PATCH v2 2/9] drm: bridge: Add LVDS encoder driver, Laurent Pinchart
  • [PATCH v2 5/9] drm: Add encoder_type field to the drm_bridge structure, Laurent Pinchart
  • [PATCH v2 8/9] drm: rcar-du: Replace manual bridge implementation with DRM bridge, Laurent Pinchart
  • [PATCH v2 9/9] drm: rcar-du: Initialize encoder's type based on the bridge's type, Laurent Pinchart
  • [PATCH v2 4/9] drm: bridge: lvds-encoder: Add thine, thc63lvdm83d compatible string, Laurent Pinchart
  • [PATCH v2 6/9] drm: bridge: Set bridges' encoder type, Laurent Pinchart
  • [PATCH v2 7/9] drm: Set on-chip bridges' encoder type, Laurent Pinchart