From: Weijie Yuan <wy@wyuan.org>
To: 岳秉坤 <yuebingkun@kylinos.cn>
Cc: mchehab@kernel.org, tony.luck@intel.com, corbet@lwn.net,
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
Subject: Re: [PATCH v2 1/3] Documentation: fix "should be use" grammar in ABI README
Date: Tue, 28 Jul 2026 12:24:05 +0800 [thread overview]
Message-ID: <amgu5cFN_imQgMf-@wyuan.org> (raw)
In-Reply-To: <20260728041213.52820-2-yuebingkun@kylinos.cn>
Hi 秉坤,
On Tue, Jul 28, 2026 at 12:12:11PM +0800, 岳秉坤 wrote:
> Fix "should be use" -> "should use" in Documentation/ABI/README.
The diff below already documents that the changes is in
"Documentation/ABI/README". I'm not sure if it is proper to write like
this. But I also do not know what's the best practice to write commit
messages for typos. Hope some friends could provide a better answer ;-)
Of course, if the maintainer thinks it's okay, I'll be definitely fine
with it.
> Signed-off-by: 岳秉坤 <yuebingkun@kylinos.cn>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
Usually, your "Signed-off-by" should be the last trailer.
> ---
> Documentation/ABI/README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/README b/Documentation/ABI/README
> index 315fffe1f831f..27c962e6a872c 100644
> --- a/Documentation/ABI/README
> +++ b/Documentation/ABI/README
Thanks.
next prev parent reply other threads:[~2026-07-28 4:24 UTC|newest]
Thread overview: 11+ 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 [this message]
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 岳秉坤
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=amgu5cFN_imQgMf-@wyuan.org \
--to=wy@wyuan.org \
--cc=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