From: Hemanth Selam <hemanth.selam@gmail.com>
To: 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>,
Lyude Paul <lyude@redhat.com>, Danilo Krummrich <dakr@kernel.org>,
Zack Rusin <zack.rusin@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm: fix repeated words in comments
Date: Mon, 7 Sep 2026 09:54:00 +0530 [thread overview]
Message-ID: <20260907042402.12893-4-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904120430.17224-3-hemanth.selam@gmail.com>
Thanks all for looking, and point taken on the churn - I am dropping this
series and will not resend it.
One correction worth recording before I do, because it is a mistake rather
than a matter of taste:
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c
"Add a view and the surface it's pointing to to the validation list"
That is correct English. "the surface it's pointing to" ends the clause
and "to the validation list" begins the next; my patch deleted a word that
the sentence needs.
Natalie is also right that the dmem hunk is already fixed by 23df2e995df85
in drm-misc-next.
next prev parent reply other threads:[~2026-09-07 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904120430.17224-1-hemanth.selam@gmail.com>
2026-09-04 12:04 ` [PATCH 1/3] drm: fix typos in comments Hemanth Selam
2026-09-04 12:13 ` Philipp Stanner
2026-09-04 12:34 ` Tomi Valkeinen
2026-09-04 13:19 ` Luca Ceresoli
2026-09-04 12:32 ` Natalie Vock
2026-09-04 12:04 ` [PATCH 2/3] drm: fix repeated words " Hemanth Selam
2026-09-04 12:09 ` sashiko-bot
2026-09-07 4:24 ` Hemanth Selam [this message]
2026-09-04 12:04 ` [PATCH 3/3] drm/vmwgfx: fix repeated word in log message Hemanth Selam
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=20260907042402.12893-4-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@broadcom.com \
/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