From: Jonathan Corbet <corbet@lwn.net>
To: 岳秉坤 <yuebingkun@kylinos.cn>, mchehab@kernel.org, tony.luck@intel.com
Cc: rdunlap@infradead.org, shiju.jose@huawei.com,
jacopo.mondi@ideasonboard.com, laurent.pinchart@ideasonboard.com,
hverkuil+cisco@kernel.org, sakari.ailus@linux.intel.com,
linux-doc@vger.kernel.org, linux-edac@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
岳秉坤 <yuebingkun@kylinos.cn>
Subject: Re: [PATCH v2 0/3] Documentation: fix a few typo and wording issues
Date: Mon, 03 Aug 2026 12:22:52 -0600 [thread overview]
Message-ID: <87jyq7ysg3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260728041213.52820-1-yuebingkun@kylinos.cn>
岳秉坤 <yuebingkun@kylinos.cn> writes:
> Hi,
>
> This series fixes a few small documentation issues (spelling/wording)
> across Documentation/ files. Each patch targets a single subsystem's
> docs so the respective maintainers can pick them up independently.
> These changes are limited to spelling and wording corrections and do
> not change behavior.
>
> I am a newcomer to the Linux community, and I am eager to contribute
> and learn through small, helpful fixes like this one.
>
> Changes in v2:
> - Split the original single combined patch into per-subsystem patches,
> per Randy Dunlap's feedback on v1.
> - Moved the "newcomer" note out of the individual commit messages; it
> now lives only in this cover letter.
> - Collected Acked-by from Randy Dunlap <rdunlap@infradead.org>. The
> content per-file is unchanged from v1, so the Ack is carried forward
> on each patch.
>
> 岳秉坤 (3):
> Documentation: fix "should be use" grammar in ABI README
> Documentation: fix "readng" typo in EDAC memory-repair ABI doc
> Documentation: fix "thare are" typo in V4L subdev routing doc
>
> Documentation/ABI/README | 2 +-
> Documentation/ABI/testing/sysfs-edac-memory-repair | 2 +-
> .../userspace-api/media/v4l/vidioc-subdev-g-routing.rst | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
The first and third problems have already been fixed by others; I have
applied the EDAC fix.
Thanks,
jon
prev parent reply other threads:[~2026-08-03 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 4:12 [PATCH v2 0/3] Documentation: fix a few typo and wording issues 岳秉坤
2026-07-28 4:12 ` [PATCH v2 1/3] Documentation: fix "should be use" grammar in ABI README 岳秉坤
2026-07-28 4:24 ` Weijie Yuan
2026-07-28 4:31 ` Randy Dunlap
2026-07-28 5:48 ` Weijie Yuan
2026-07-28 16:55 ` Randy Dunlap
2026-07-28 17:15 ` Weijie Yuan
2026-07-28 17:25 ` Luck, Tony
2026-07-28 17:51 ` Weijie Yuan
2026-07-28 4:12 ` [PATCH v2 2/3] Documentation: fix "readng" typo in EDAC memory-repair ABI doc 岳秉坤
2026-07-28 4:12 ` [PATCH v2 3/3] Documentation: fix "thare are" typo in V4L subdev routing doc 岳秉坤
2026-08-03 18:22 ` 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=87jyq7ysg3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=hverkuil+cisco@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shiju.jose@huawei.com \
--cc=tony.luck@intel.com \
--cc=yuebingkun@kylinos.cn \
/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