From: Seyediman Seyedarab <imandevel@gmail.com>
To: linux-doc@vger.kernel.org
Cc: skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
corbet@lwn.net, Seyediman Seyedarab <ImanDevel@gmail.com>
Subject: [PATCH] drm/doc: fix minor grammatical issues
Date: Mon, 3 Feb 2025 18:40:46 -0500 [thread overview]
Message-ID: <20250203234046.5114-1-ImanDevel@gmail.com> (raw)
The following grammatical issues have been fixed:
- Corrected subject-verb agreement
- Replaced incorrect noun "setup" with the correct verb form "set up."
Signed-off-by: Seyediman Seyedarab <ImanDevel@gmail.com>
---
Documentation/gpu/drm-kms.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
index abfe220764e1..6a3ae069c829 100644
--- a/Documentation/gpu/drm-kms.rst
+++ b/Documentation/gpu/drm-kms.rst
@@ -6,7 +6,7 @@ Drivers must initialize the mode setting core by calling
drmm_mode_config_init() on the DRM device. The function
initializes the :c:type:`struct drm_device <drm_device>`
mode_config field and never fails. Once done, mode configuration must
-be setup by initializing the following fields.
+be set up by initializing the following fields.
- int min_width, min_height; int max_width, max_height;
Minimum and maximum width and height of the frame buffers in pixel
@@ -253,7 +253,7 @@ rollback:
should not interfere, and not get stalled due to output routing changing on
different CRTCs.
-Taken all together there's two consequences for the atomic design:
+Taken all together there are two consequences for the atomic design:
- The overall state is split up into per-object state structures:
:c:type:`struct drm_plane_state <drm_plane_state>` for planes, :c:type:`struct
--
2.48.1
reply other threads:[~2025-02-03 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250203234046.5114-1-ImanDevel@gmail.com \
--to=imandevel@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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