[Intel-xe] [PATCH 1/4] drm/doc/rfc: No STAGING out of drivers/staging.

[Lucas De Marchi]

On Tue, Aug 29, 2023 at 12:30:01PM -0400, Rodrigo Vivi wrote:
>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
>Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>

Agreed. The STAGING config is something specifically for drivers/staging
as noted in the previous discussion. If other subsystems want to re-use
it, then there would be more to do to cause a taint.  It could also be
confusing to cause that taint for drivers outside drivers/staging.

Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com>

Lucas De Marchi

>---
> Documentation/gpu/rfc/xe.rst | 6 ------
> 1 file changed, 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
> ====================
>
>-- 
>2.41.0
>