drm/doc: More fine-tuning on userspace review requirements

[sfrench/cifs-2.6.git] / Documentation / gpu / drm-uapi.rst

diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 05874d09820c25d6a2708bfbbe01e2daa2c440bd..f368e58fb727b1f63fe17f728bc72cc2ae81cdb9 100644 (file)
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -85,9 +85,9 @@ leads to a few additional requirements:
 - The userspace side must be fully reviewed and tested to the standards of that
   userspace project. For e.g. mesa this means piglit testcases and review on the
   mailing list. This is again to ensure that the new interface actually gets the
-  job done.  The userspace-side reviewer should also provide at least an
-  Acked-by on the kernel uAPI patch indicating that they've looked at how the
-  kernel side is implementing the new feature being used.
+  job done.  The userspace-side reviewer should also provide an Acked-by on the
+  kernel uAPI patch indicating that they believe the proposed uAPI is sound and
+  sufficiently documented and validated for userspace's consumption.
 
 - The userspace patches must be against the canonical upstream, not some vendor
   fork. This is to make sure that no one cheats on the review and testing