public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	attreyee-muk <tintinm2017@gmail.com>,
	bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/PCI: fix spelling mistake in boot-interrupts
Date: Sat, 23 Dec 2023 15:09:53 -0700	[thread overview]
Message-ID: <87jzp4605q.fsf@meer.lwn.net> (raw)
In-Reply-To: <6026d9b5-dd6f-43f8-acc7-9cc77bdb3df3@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> Hi,
>
> On 12/23/23 10:44, attreyee-muk wrote:
>> Correct to “re-enabled” from “reenabled”.
>> 
>> Signed-off-by: Attreyee Mukherjee <tintinm2017@gmail.com>
>
> Is "reenabled" confusing? I don't have a problem with it, but
> one web page [1] says that it's OK to use "re-" if not having
> the hyphen can be confusing.
>
> [1] https://www.grammarbook.com/blog/hyphens/hyphens-with-the-prefix-re/
>
> OTOH, some web sites say the "reenable" is OK, at least as an
> alternative spelling.

Either is probably fine; so I'm not quite sure why this is worth
changing?

Thanks,

jon

  reply	other threads:[~2023-12-23 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 18:44 [PATCH] Documentation/PCI: fix spelling mistake in boot-interrupts attreyee-muk
2023-12-23 19:28 ` Randy Dunlap
2023-12-23 22:09   ` Jonathan Corbet [this message]
2023-12-28 23:41 ` Bjorn Helgaas

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=87jzp4605q.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bhelgaas@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tintinm2017@gmail.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