Skip to content

Commit d29e112

Browse files
committed
drm/doc/rfc: No STAGING out of drivers/staging.
Also the uapi should be reviewed and scrutinized before xe is accepted upstream and we shouldn't cause regression. Link: https://lore.kernel.org/all/20230630100059.122881-1-thomas.hellstrom@linux.intel.com Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230829163005.54067-1-rodrigo.vivi@intel.com
1 parent 9eeba91 commit d29e112

1 file changed

Lines changed: 0 additions & 6 deletions

File tree

Documentation/gpu/rfc/xe.rst

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -67,12 +67,6 @@ platforms.
6767

6868
When the time comes for Xe, the protection will be lifted on Xe and kept in i915.
6969

70-
Xe driver will be protected with both STAGING Kconfig and force_probe. Changes in
71-
the uAPI are expected while the driver is behind these protections. STAGING will
72-
be removed when the driver uAPI gets to a mature state where we can guarantee the
73-
‘no regression’ rule. Then force_probe will be lifted only for future platforms
74-
that will be productized with Xe driver, but not with i915.
75-
7670
Xe – Pre-Merge Goals
7771
====================
7872

0 commit comments

Comments
 (0)