Back to bug 94393
Who | When | What | Removed | Added |
---|---|---|---|---|
ricardo.vega | 2016-03-04 15:41:49 UTC | i915 platform | BXT | |
ramix.ben.hassine | 2016-03-04 17:50:44 UTC | i915 platform | KBL | |
ramix.ben.hassine | 2016-03-04 17:56:02 UTC | Summary | [APL] kms_chv_cursor_fail all subtests are failing | [APL KBL] kms_chv_cursor_fail all subtests are failing |
elio.martinez.monroy | 2016-03-16 17:47:55 UTC | i915 platform | BDW | |
Summary | [APL KBL] kms_chv_cursor_fail all subtests are failing | [APL KBL BDW] kms_chv_cursor_fail all subtests are failing | ||
humberto.i.perez.rodriguez | 2016-03-17 16:33:59 UTC | Summary | [APL KBL BDW] kms_chv_cursor_fail all subtests are failing | [APL/KBL/BDW] kms_chv_cursor_fail all subtests are failing |
yann.argotti | 2016-03-18 16:16:23 UTC | i915 features | display/Other | |
christophe.prigent | 2016-04-19 10:14:19 UTC | i915 platform | KBL | |
Summary | [APL/KBL/BDW] kms_chv_cursor_fail all subtests are failing | [APL/BDW] kms_chv_cursor_fail all subtests are failing | ||
yann.argotti | 2016-04-29 11:04:10 UTC | Priority | medium | high |
maria.g.perez.ibarra | 2016-05-26 21:59:57 UTC | Summary | [APL/BDW] kms_chv_cursor_fail all subtests are failing | [APL/BDW/KBL] kms_chv_cursor_fail all subtests are failing |
i915 platform | KBL | |||
bugs | 2016-06-08 11:29:55 UTC | Status | NEW | NEEDINFO |
bugs | 2016-06-09 07:05:14 UTC | Status | NEEDINFO | RESOLVED |
Resolution | --- | FIXED | ||
luis.botello.ortega | 2016-06-22 16:32:20 UTC | i915 platform | SKL | |
Summary | [APL/BDW/KBL] kms_chv_cursor_fail all subtests are failing | [APL/BDW/KBL/SKL] kms_chv_cursor_fail all subtests are failing | ||
christophe.prigent | 2016-07-06 12:25:12 UTC | i915 platform | BXT | |
Summary | [APL/BDW/KBL/SKL] kms_chv_cursor_fail all subtests are failing | [BDW/KBL/SKL] kms_chv_cursor_fail all subtests are failing | ||
elizabethx.de.la.torre.mena | 2017-07-24 22:42:43 UTC | Status | RESOLVED | CLOSED |
Back to bug 94393
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.