[PATCH] fixed typo in the DRM UAPI documentation.

[PATCH] fixed typo in the DRM UAPI documentation.

[Ayash-Bera]

fix a minor typo for the drm-uapi Documentation. 

Signed-off-by: Ayash-Bera <ayashbera@gmail.com>
---
 Documentation/gpu/drm-uapi.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 69f72e71a96e..64e002c6383c 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -518,7 +518,7 @@ ENOSPC:
 EPERM/EACCES:
         Returned for an operation that is valid, but needs more privileges.
         E.g. root-only or much more common, DRM master-only operations return
-        this when called by unpriviledged clients. There's no clear
+        this when called by unprivileged clients. There's no clear
         difference between EACCES and EPERM.
 
 ENODEV:
-- 
2.50.1

[PATCH] fixed typo in the DRM UAPI documentation.

[Ayash-Bera]

fixed a minor typo for the drm-uapi documentation 

Signed-off-by: Ayash-Bera <ayashbera@gmail.com>
---
 Documentation/gpu/drm-uapi.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 69f72e71a96e..64e002c6383c 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -518,7 +518,7 @@ ENOSPC:
 EPERM/EACCES:
         Returned for an operation that is valid, but needs more privileges.
         E.g. root-only or much more common, DRM master-only operations return
-        this when called by unpriviledged clients. There's no clear
+        this when called by unprivileged clients. There's no clear
         difference between EACCES and EPERM.
 
 ENODEV:
-- 
2.50.1

Re: [PATCH] fixed typo in the DRM UAPI documentation.

[Brigham Campbell]

Hi, Ayash-Bera.

On Tue Jul 29, 2025 at 2:20 PM MDT, Ayash-Bera wrote:
> fixed a minor typo for the drm-uapi documentation 

By common convention, this should be written in an imperative tone and
should be punctuated correctly. For example:

"Fix a minor typo for the drm-uapi documentation."

The subject of this email should also be imperative, but unlike the body
of your patch, should not end in a period. See
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#the-canonical-patch-format
for more information.

This patch should have also been sent to drm subsystem maintainers. Did
you run get_maintainer.pl to get a list of recipients?

Reviewed-by: Brigham Campbell <me@brighamcampbell.com>