From: Jonathan Corbet <corbet@lwn.net>
To: Brigham Campbell <me@brighamcampbell.com>,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Brigham Campbell <me@brighamcampbell.com>
Subject: Re: [PATCH RESEND] drm: docs: Fix typo in introduction.rst
Date: Fri, 11 Jul 2025 06:51:53 -0600 [thread overview]
Message-ID: <87tt3ix53q.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250711030157.124778-1-me@brighamcampbell.com>
Brigham Campbell <me@brighamcampbell.com> writes:
> Fix typo in Documentation/gpu/introduction.rst
>
> Link: https://lore.kernel.org/all/20250620180258.132160-1-me@brighamcampbell.com/
> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
> ---
>
> This patch has received no response as of June 20th. If it's
> unacceptable for whatever reason, please let me know and I'll drop it.
> This is the only typo I happened across while reading the document. I
> scanned it for more typos when I prepared this patch, but found none.
The patch seems fine, though I wouldn't put a Link: tag for a previous
version like that.
I didn't apply it because the DRM folks generally handle their own
documentation patches. I'm assuming this one just fell through the
cracks; resending it was the right thing to do.
Thanks,
jon
prev parent reply other threads:[~2025-07-11 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 3:01 [PATCH RESEND] drm: docs: Fix typo in introduction.rst Brigham Campbell
2025-07-11 12:51 ` Jonathan Corbet [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=87tt3ix53q.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@brighamcampbell.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