All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Seyediman Seyedarab <imandevel@gmail.com>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] drm/doc: fix minor grammatical issues
Date: Sun, 16 Feb 2025 08:27:15 -0700	[thread overview]
Message-ID: <87cyfhvrjg.fsf@trenco.lwn.net> (raw)
In-Reply-To: <435n35tqqhg63u362uyttit2kqx6qfr6cny6ap5rxigyvg7sx4@ewumuzncwczq>

Seyediman Seyedarab <imandevel@gmail.com> writes:

> On 25/02/03 06:40PM, Seyediman Seyedarab wrote:
>> 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
>> 
>
> Just following up on this patch I sent on 25/02/03. It's a small
> typo fix in the drm-kms documentation, nothing major, but I just
> wanted to make sure it hasn't slipped through the cracks.
> Appreciate any feedback when you get a chance. Thanks!

Please resend that patch after using scripts/get_maintainer.pl to get
the proper recipient list.  The DRM folks handle their own documentation
patches, so I can't apply this one.

Thanks,

jon

  reply	other threads:[~2025-02-16 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 23:40 [PATCH] drm/doc: fix minor grammatical issues Seyediman Seyedarab
2025-02-16 13:21 ` Seyediman Seyedarab
2025-02-16 15:27   ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-16 16:10 Seyediman Seyedarab

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=87cyfhvrjg.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=imandevel@gmail.com \
    --cc=linux-doc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.