diff options
author | Rodrigo Vivi <[email protected]> | 2023-08-29 12:30:01 -0400 |
---|---|---|
committer | Rodrigo Vivi <[email protected]> | 2023-09-07 17:27:12 -0400 |
commit | d29e112ab8d4fea3bf82c7b023c6e65ed2c0e5eb (patch) | |
tree | 3aeeceb234c7616c14eef32703b8fa0a5448f899 | |
parent | 9eeba919dd0f524f73feeeef82f3ca877f9ccce4 (diff) |
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/[email protected]
Acked-by: Daniel Vetter <[email protected]>
Reviewed-by: Lucas De Marchi <[email protected]>
Signed-off-by: Rodrigo Vivi <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
-rw-r--r-- | Documentation/gpu/rfc/xe.rst | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/Documentation/gpu/rfc/xe.rst b/Documentation/gpu/rfc/xe.rst index 2516fe141db6..3d2181bf3dad 100644 --- a/Documentation/gpu/rfc/xe.rst +++ b/Documentation/gpu/rfc/xe.rst @@ -67,12 +67,6 @@ platforms. When the time comes for Xe, the protection will be lifted on Xe and kept in i915. -Xe driver will be protected with both STAGING Kconfig and force_probe. Changes in -the uAPI are expected while the driver is behind these protections. STAGING will -be removed when the driver uAPI gets to a mature state where we can guarantee the -‘no regression’ rule. Then force_probe will be lifted only for future platforms -that will be productized with Xe driver, but not with i915. - Xe – Pre-Merge Goals ==================== |