From: Randy Dunlap <rdunlap@infradead.org>
To: Hardik Kumar <hardikxk@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/gpu: Fix spelling mistakes in todo gpu doc
Date: Thu, 3 Sep 2026 10:27:49 -0700 [thread overview]
Message-ID: <9e53e154-1b4e-49f4-a028-a50af0fbadf3@infradead.org> (raw)
In-Reply-To: <20260903-docs-gpu-todo-v1-1-be712c8f67a0@gmail.com>
On 9/3/26 10:04 AM, Hardik Kumar wrote:
> Fix some obvious typos in the todo.rst doc.
>
> Correct spellings of incorrect words.
> Fix an article usage.
>
> Signed-off-by: Hardik Kumar <hardikxk@gmail.com>
> ---
> Documentation/gpu/todo.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index 14cf37590..187932554 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -277,8 +277,8 @@ Various hold-ups:
> - Need to switch to drm_gem_fb_create(), as now drm_gem_fb_create() checks for
> valid formats for atomic drivers.
>
> -- Many drivers subclass drm_framebuffer, we'd need a embedding compatible
> - version of the varios drm_gem_fb_create functions. Maybe called
> +- Many drivers subclass drm_framebuffer, we'd need an embedding compatible
> + version of the various drm_gem_fb_create functions. Maybe called
LGTM except for the comma splice above, which you weren't
attempting to repair. Thanks.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> drm_gem_fb_create/_with_dirty/_with_funcs as needed.
>
> Contact: Simona Vetter
> @@ -303,7 +303,7 @@ everything after it has done the write-protect/mkwrite trickery:
>
> vma->vm_page_prot = pgprot_wrprotect(vma->vm_page_prot);
>
> -- Set the mkwrite and fsync callbacks with similar implementions to the core
> +- Set the mkwrite and fsync callbacks with similar implementations to the core
> fbdev defio stuff. These should all work on plain ptes, they don't actually
> require a struct page. uff. These should all work on plain ptes, they don't
> actually require a struct page.
> @@ -465,7 +465,7 @@ be turned into a WARN_ON() or somehow made louder.
> At the moment, we expect that we may still encounter the warnings in the
> drm_panel core when using panel-simple and panel-edp. Since those panel
> drivers are used with a lot of different DRM modeset drivers they still
> -make an extra effort to disable/unprepare the panel themsevles at shutdown
> +make an extra effort to disable/unprepare the panel themselves at shutdown
> time. Specifically we could still encounter those warnings if the panel
> driver gets shutdown() _before_ the DRM modeset driver and the DRM modeset
> driver properly calls drm_atomic_helper_shutdown() in its own shutdown()
> @@ -891,7 +891,7 @@ Querying errors from drm_syncobj
> ================================
>
> The drm_syncobj container can be used by driver independent code to signal
> -complection of submission.
> +completion of submission.
>
> One minor feature still missing is a generic DRM IOCTL to query the error
> status of binary and timeline drm_syncobj.
>
> ---
> base-commit: 66498c75b4f8017f62d720d9b59675bdf3abce91
> change-id: 20260903-docs-gpu-todo-31116c645874
>
> Best regards,
--
~Randy
prev parent reply other threads:[~2026-09-03 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 17:04 Hardik Kumar
2026-09-03 17:27 ` Randy Dunlap [this message]
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=9e53e154-1b4e-49f4-a028-a50af0fbadf3@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hardikxk@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®