public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Jonathan Corbet" <corbet@lwn.net>,
	"Derek J . Clark" <derekjohn.clark@gmail.com>,
	"Ninad Naik" <ninadnaik07@gmail.com>,
	"Armin Wolf" <W_Armin@gmx.de>,
	skhan@linuxfoundation.org
Cc: "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	me@brighamcampbell.com, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] Documentation: fix spelling mistake "Minumum" -> "Minimum"
Date: Mon, 20 Apr 2026 14:07:53 -0400	[thread overview]
Message-ID: <caeb609a-499f-4eab-91a2-2d85665631ea@app.fastmail.com> (raw)
In-Reply-To: <87fr4qw2jy.fsf@trenco.lwn.net>


On Mon, Apr 20, 2026, at 2:47 AM, Jonathan Corbet wrote:
> "Derek J. Clark" <derekjohn.clark@gmail.com> writes:
>
>> The MOF spelling mistakes are well known. We've left them is as to
>> ensure match with what the hardware actually reports.
>>
>> See: https://lore.kernel.org/platform-driver-x86/cfd7977e-d612-4e08-a68a-65fed8e164b6@gmx.de
>>
>> I suppose if we're going to continue getting these types or PR I
>> should add a note to the documentation. I'll add that soon.
>
> Perhaps worth adding, but I'm not sure I would expect it to help.  The
> people generating these patches aren't putting much attention into the
> context surrounding them.
>
I'd forgotten that previous discussion - sorry.

Part of the problem (I know I had this many years ago when I got started) is being told the best way to get involved in kernel development and learn the process is to find small things to fix (spelling mistakes, documentation, comments etc). I suspect that's accelerated with AI identifying them too :)

What if we fix the typo, and add a comment highlighting that the vendor documentation/MOF/whatever is wrong? Then everybody is 'happy'? (or at least we'll get less emails about it)

Mark

      reply	other threads:[~2026-04-20 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-19 17:08 [PATCH] Documentation: fix spelling mistake "Minumum" -> "Minimum" Ninad Naik
2026-04-19 22:10 ` Mark Pearson
2026-04-19 22:24   ` Derek J. Clark
2026-04-20  6:47     ` Jonathan Corbet
2026-04-20 18:07       ` Mark Pearson [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=caeb609a-499f-4eab-91a2-2d85665631ea@app.fastmail.com \
    --to=mpearson-lenovo@squebb.ca \
    --cc=W_Armin@gmx.de \
    --cc=corbet@lwn.net \
    --cc=derekjohn.clark@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=ninadnaik07@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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