On Wed, Mar 18, 2020 at 06:31:16PM +0000, Chris Wilson wrote:
Quoting Ville Syrjala (2020-03-18 18:25:18)
From: Ville Syrjälä ville.syrjala@linux.intel.com
drm_mode_config_init() may not have been called when the driver/device doesn't support modeset. That will cause drm_mode_config_validate() to oops. Skip the validation for !modeset.
TODO: We may want to consider calling drm_mode_config_init() unconditionally to avoid similar issues elsewhere...
Fixes: 74d2aacbe840 ("drm: Validate encoder->possible_clones") Signed-off-by: Ville Syrjälä ville.syrjala@linux.intel.com
Reviewed-by: Chris Wilson chris@chris-wilson.co.uk
Thanks. Looks like this gets BAT up and running again so pushing w/o waiting for shards.
Sorry about the mess everyone. CI had turned a blind eye on the regressing series and I didn't notice that fact. I need to adjust my brain regex to look for *all* CI mails, not just the failures.