mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux DRI Development <dri-devel@lists.freedesktop.org>
Cc: 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>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Pranav Tyagi <pranav.tyagi03@gmail.com>
Subject: Re: [PATCH] Documentation: vgaarbiter: Fix grammar
Date: Tue, 18 Mar 2025 08:43:31 -0600	[thread overview]
Message-ID: <87a59icsbw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250318041249.20786-2-bagasdotme@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> From: Pranav Tyagi <pranav.tyagi03@gmail.com>
>
> Correct grammar issues:
>
> - Fix "co-exist" subject-verb agreement
> - Correct plural form of "server" in context of more than one legacy
>   devices
> - Use passive mood for intro sentence of libpciaccess section
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
> Link: https://lore.kernel.org/r/20250220164946.18007-1-pranav.tyagi03@gmail.com
> [Bagas: massage commit message]
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
>
> I have to carry the original patch [1] because DRM maintainers doesn't seem
> to apply that AFAIK. Jon, would you like to apply this patch before the
> merge window in case DRM people don't apply this either?

The DRM folks manage their own docs.  I'm certainly not going to
circumvent them during -rc7 for a patch like this.

jon

  reply	other threads:[~2025-03-18 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  4:12 Bagas Sanjaya
2025-03-18 14:43 ` Jonathan Corbet [this message]
2025-03-19  3:44   ` Bagas Sanjaya
2025-03-19 14:12 ` Maxime Ripard

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=87a59icsbw.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=pranav.tyagi03@gmail.com \
    --cc=simona@ffwll.ch \
    --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®