From: Jonathan Corbet <corbet@lwn.net>
To: Nauman Sabir <officialnaumansabir@gmail.com>, linux-doc@vger.kernel.org
Cc: tj@kernel.org, Nauman Sabir <officialnaumansabir@gmail.com>
Subject: Re: [PATCH v4] Documentation: Fix typos and grammatical errors
Date: Fri, 16 Jan 2026 11:13:35 -0700 [thread overview]
Message-ID: <87ms2do27k.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260115230110.7734-1-officialnaumansabir@gmail.com>
Nauman Sabir <officialnaumansabir@gmail.com> writes:
> Fix various typos and grammatical errors across documentation files:
>
> - Fix missing preposition 'in' in process/changes.rst
> - Correct 'result by' to 'result from' in admin-guide/README.rst
> - Fix 'before hand' to 'beforehand' in cgroup-v1/hugetlb.rst
> - Correct 'allows to limit' to 'allows limiting' in hugetlb.rst,
> cgroup-v2.rst, and kconfig-language.rst
> - Fix 'needs precisely know' to 'needs to precisely know'
> - Correct 'overcommited' to 'overcommitted' in hugetlb.rst
> - Fix subject-verb agreement: 'never causes' to 'never cause'
> - Fix 'there is enough' to 'there are enough' in hugetlb.rst
> - Fix 'metadatas' to 'metadata' in filesystems/erofs.rst
> - Fix 'hardwares' to 'hardware' in scsi/ChangeLog.sym53c8xx
>
> Signed-off-by: Nauman Sabir <officialnaumansabir@gmail.com>
> ---
> Resending as a standalone patch. Apologies for the confusion caused by
> the previous submission, which was incorrectly sent as part of a 3-patch
> series. Each patch targets a different subsystem and should be reviewed
> and applied independently. Please ignore the previous submission:
> <20260112160820.19075-1-officialnaumansabir@gmail.com>
This patch did not apply cleanly to docs-next - I had to use
--whitespace=fix. I'm guessing that your mailer messed up the trailing
whitespace in ChangeLog.sym53c8xx.
Now, honestly, that file should not really exist at all IMO... but it
would also be good to avoid this kind of problem with future patches.
I'd suggest emailing this patch to yourself until you get to a point
where you can apply it to a clean tree.
Thanks,
jon
prev parent reply other threads:[~2026-01-16 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 23:01 [PATCH v4] Documentation: Fix typos and grammatical errors Nauman Sabir
2026-01-16 8:07 ` Tejun Heo
2026-01-16 18:13 ` 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=87ms2do27k.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=officialnaumansabir@gmail.com \
--cc=tj@kernel.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