loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <siyanteng@loongson.cn>
To: chenhuacai@kernel.org, alexs@kernel.org, bobwxc@email.cn,
	seakeel@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
	corbet@lwn.net, kernel@xen0n.name, jiaxun.yang@flygoat.com,
	linux-doc@vger.kernel.org, siyanteng01@gmail.com,
	loongarch@lists.linux.dev
Subject: [PATCH v4 0/2] docs: Improve loongarch documents
Date: Fri, 17 Jun 2022 20:47:53 +0800	[thread overview]
Message-ID: <cover.1655469906.git.siyanteng@loongson.cn> (raw)

v4:
Modify commit message.

v3:
Modify Subject.

v2:
Fix ``inline literals``.
Delete "注:" of zh_CN patch.
Add fix tag.

v1:
Rewrite all the notes in the loongarch document.
Note is an admonition, let's use the directives
implemented in the reference reStructuredText parser.
About reStructuredText Directives,
see <https://docutils.sourceforge.io/docs/ref/rst/directives.html>

Yanteng Si (2):
  docs/LoongArch: Fix notes rendering by using reST directives
  docs/zh_CN/LoongArch: Fix notes rendering by using reST directives

 Documentation/loongarch/introduction.rst      | 15 ++++++++-----
 Documentation/loongarch/irq-chip-model.rst    | 22 +++++++++++--------
 .../zh_CN/loongarch/introduction.rst          | 14 +++++++-----
 .../zh_CN/loongarch/irq-chip-model.rst        | 14 +++++++-----
 4 files changed, 38 insertions(+), 27 deletions(-)

-- 
2.27.0


             reply	other threads:[~2022-06-17 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 12:47 Yanteng Si [this message]
2022-06-17 12:47 ` [PATCH v4 1/2] docs/LoongArch: Fix notes rendering by using reST directives Yanteng Si
2022-06-17 12:47 ` [PATCH v4 2/2] docs/zh_CN/LoongArch: " Yanteng Si
2022-06-17 14:01   ` WANG Xuerui
2022-06-17 14:05 ` [PATCH v4 0/2] docs: Improve loongarch documents Huacai Chen

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=cover.1655469906.git.siyanteng@loongson.cn \
    --to=siyanteng@loongson.cn \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-doc@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=seakeel@gmail.com \
    --cc=siyanteng01@gmail.com \
    /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).