From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>, maennich@google.com
Cc: linux-doc@vger.kernel.org, bobwxc@email.cn,
chenhuacai@kernel.org, siyanteng01@gmail.com,
Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH] docs/core-api: Consistent code style
Date: Mon, 03 May 2021 16:53:14 -0600 [thread overview]
Message-ID: <87eeenh1k5.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210428100720.1076276-1-siyanteng@loongson.cn>
Yanteng Si <siyanteng@loongson.cn> writes:
> all `example` in this file should be replaced with ``example``.
>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> ---
> Documentation/core-api/symbol-namespaces.rst | 26 ++++++++++----------
> 1 file changed, 13 insertions(+), 13 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2021-05-03 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 10:07 [PATCH] docs/core-api: Consistent code style Yanteng Si
2021-04-28 10:50 ` Matthias Maennich
2021-05-03 22:53 ` 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=87eeenh1k5.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=maennich@google.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.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;
as well as URLs for NNTP newsgroup(s).