From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: daniel.vetter@ffwll.ch, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 1/4] drm/doc/rfc: No STAGING out of drivers/staging.
Date: Thu, 31 Aug 2023 10:31:07 +0200 [thread overview]
Message-ID: <ZPBPy9K/Mx820Z3q@phenom.ffwll.local> (raw)
In-Reply-To: <20230829163005.54067-1-rodrigo.vivi@intel.com>
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@intel.com>
On the series:
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
But also, I really don't want to be the gatekeeper for "is xe ready for
merging", so at least for the last two patches I think an ack from Danilo
that there's indeed a rough consensus/plan is much more important than my
own. The first two don't need that, because there was no "build dri-devel
consensus" aspect to those.
And for the sched side I guess an ack from Christian or maybe some of the
other in-flight drivers (Lina or Boris?), with maybe an ack from Danilo
for the long running compute stuff (or whoever cares about that, I don't
think amd is working on extracting the amdkfd trickery, but maybe they
need the sched support when they add real compute to the render driver
too) is again much more important than me dropping an ack from the
sidelines.
Cheers, Sima
> ---
> 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
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-08-31 8:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:30 [Intel-xe] [PATCH 1/4] drm/doc/rfc: No STAGING out of drivers/staging Rodrigo Vivi
2023-08-29 16:30 ` [Intel-xe] [PATCH 2/4] drm/doc/rfc: Mark Dev_coredump as completed Rodrigo Vivi
2023-08-29 16:30 ` [Intel-xe] [PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete Rodrigo Vivi
2023-08-31 19:10 ` Rodrigo Vivi
2023-09-04 21:32 ` Danilo Krummrich
2023-09-06 17:57 ` Rodrigo Vivi
2023-08-29 16:30 ` [Intel-xe] [PATCH 4/4] drm/doc/rfc: Mark GPU VA " Rodrigo Vivi
2023-08-31 19:17 ` Rodrigo Vivi
2023-09-04 21:39 ` Danilo Krummrich
2023-09-06 18:03 ` Rodrigo Vivi
2023-08-29 16:44 ` [Intel-xe] ✗ CI.Patch_applied: failure for series starting with [1/4] drm/doc/rfc: No STAGING out of drivers/staging Patchwork
2023-08-29 17:35 ` [Intel-xe] [PATCH 1/4] " Lucas De Marchi
2023-08-31 8:31 ` Daniel Vetter [this message]
2023-08-31 19:08 ` Rodrigo Vivi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPBPy9K/Mx820Z3q@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox