All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] drm/doc: fix minor grammatical issues
@ 2025-02-03 23:40 Seyediman Seyedarab
  2025-02-16 13:21 ` Seyediman Seyedarab
  0 siblings, 1 reply; 4+ messages in thread
From: Seyediman Seyedarab @ 2025-02-03 23:40 UTC (permalink / raw)
  To: linux-doc; +Cc: skhan, linux-kernel-mentees, corbet, Seyediman Seyedarab

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


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] drm/doc: fix minor grammatical issues
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Seyediman Seyedarab @ 2025-02-16 13:21 UTC (permalink / raw)
  To: linux-doc, corbet

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!

Seyediman

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] drm/doc: fix minor grammatical issues
  2025-02-16 13:21 ` Seyediman Seyedarab
@ 2025-02-16 15:27   ` Jonathan Corbet
  0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Corbet @ 2025-02-16 15:27 UTC (permalink / raw)
  To: Seyediman Seyedarab, linux-doc

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH] drm/doc: fix minor grammatical issues
@ 2025-02-16 16:10 Seyediman Seyedarab
  0 siblings, 0 replies; 4+ messages in thread
From: Seyediman Seyedarab @ 2025-02-16 16:10 UTC (permalink / raw)
  To: linux-doc
  Cc: airlied, simona, maarten.lankhorst, mripard, tzimmermann,
	Seyediman Seyedarab

- Corrected subject-verb agreement
- Replaced incorrect noun "setup" with the correct verb form "set up."

Signed-off-by: Seyediman Seyedarab <ImanDevel@gmail.com>
---

Resending this patch to the correct maintainers as the initial
submission was sent to the wrong recipients.

Regards,
Seyediman

 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


^ permalink raw reply related	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-02-16 16:10 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
  -- strict thread matches above, loose matches on Subject: below --
2025-02-16 16:10 Seyediman Seyedarab

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.