From: Wu XiangCheng <bobwxc@email.cn>
To: WANG Xuerui <kernel@xen0n.name>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Yanteng Si <siyanteng@loongson.cn>, Alex Shi <alexs@kernel.org>,
seakeel@gmail.com, Jonathan Corbet <corbet@lwn.net>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Yanteng Si <siyanteng01@gmail.com>,
loongarch@lists.linux.dev, WANG Xuerui <git@xen0n.name>
Subject: Re: [PATCH v3 1/2] docs/LoongArch: Fix notes rendering by using reST directives
Date: Fri, 17 Jun 2022 20:41:55 +0800 [thread overview]
Message-ID: <Yqx2k2V0ap3yD4aF@bobwxc.mipc> (raw)
In-Reply-To: <ff1edf29-8b69-29fc-5ccd-26a6d6ef8bb9@xen0n.name>
Hi all,
On Fri, Jun 17, 2022 at 07:49:22PM +0800, WANG Xuerui wrote:
> On 2022/6/17 19:05, Huacai Chen wrote:
> > Hi, Yanteng,
> >
> > On Fri, Jun 17, 2022 at 6:55 PM Yanteng Si <siyanteng@loongson.cn> wrote:
> > > "Note" is an admonition, but it doesn't render
> > > correctly, let's fix it by using reST directives.
> > I think "but it doesn't render correctly" should be "but it isn't
> > correctly rendered in HTML". How do you think, Xuerui?
> This depends on what you mean by "correctly"; actually the original
> rendering is readable, only that it's not rendered with a "note" block.
> Maybe just "Notes are better expressed with reST admonitions."?
Agree with Xuerui.
> >
> > Huacai
> > > Fixes: 0ea8ce61cb2c ("Documentation: LoongArch: Add basic documentations")
> > > Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> > > Reviewed-by: WANG Xuerui <git@xen0n.name>
> > > ---
> > > Documentation/loongarch/introduction.rst | 15 +++++++++------
> > > Documentation/loongarch/irq-chip-model.rst | 22 +++++++++++++---------
> > > 2 files changed, 22 insertions(+), 15 deletions(-)
> > >
> > > diff --git a/Documentation/loongarch/introduction.rst b/Documentation/loongarch/introduction.rst
> > > index 2bf40ad370df..216b3f390e80 100644
> > > --- a/Documentation/loongarch/introduction.rst
> > > +++ b/Documentation/loongarch/introduction.rst
> > > @@ -45,10 +45,12 @@ Name Alias Usage Preserved
> > > ``$r23``-``$r31`` ``$s0``-``$s8`` Static registers Yes
> > > ================= =============== =================== ============
> > >
> > > -Note: The register ``$r21`` is reserved in the ELF psABI, but used by the Linux
> > > -kernel for storing the percpu base address. It normally has no ABI name, but is
> > > -called ``$u0`` in the kernel. You may also see ``$v0`` or ``$v1`` in some old code,
> > > -however they are deprecated aliases of ``$a0`` and ``$a1`` respectively.
> > > +.. Note::
> > > + The register ``$r21`` is reserved in the ELF psABI, but used by the Linux
> > > + kernel for storing the percpu base address. It normally has no ABI name,
> > > + but is called ``$u0`` in the kernel. You may also see ``$v0`` or ``$v1``
> > > + in some old code,however they are deprecated aliases of ``$a0`` and ``$a1``
> > > + respectively.
> > >
> > > FPRs
> > > ----
> > > @@ -69,8 +71,9 @@ Name Alias Usage Preserved
> > > ``$f24``-``$f31`` ``$fs0``-``$fs7`` Static registers Yes
> > > ================= ================== =================== ============
> > >
> > > -Note: You may see ``$fv0`` or ``$fv1`` in some old code, however they are deprecated
> > > -aliases of ``$fa0`` and ``$fa1`` respectively.
> > > +.. Note::
> > > + You may see ``$fv0`` or ``$fv1`` in some old code, however they are
> > > + deprecated aliases of ``$fa0`` and ``$fa1`` respectively.
> > >
> > > VRs
> > > ----
> > > diff --git a/Documentation/loongarch/irq-chip-model.rst b/Documentation/loongarch/irq-chip-model.rst
> > > index 8d88f7ab2e5e..7988f4192363 100644
> > > --- a/Documentation/loongarch/irq-chip-model.rst
> > > +++ b/Documentation/loongarch/irq-chip-model.rst
> > > @@ -145,12 +145,16 @@ Documentation of Loongson's LS7A chipset:
> > >
> > > https://github.com/loongson/LoongArch-Documentation/releases/latest/download/Loongson-7A1000-usermanual-2.00-EN.pdf (in English)
> > >
> > > -Note: CPUINTC is CSR.ECFG/CSR.ESTAT and its interrupt controller described
> > > -in Section 7.4 of "LoongArch Reference Manual, Vol 1"; LIOINTC is "Legacy I/O
> > > -Interrupts" described in Section 11.1 of "Loongson 3A5000 Processor Reference
> > > -Manual"; EIOINTC is "Extended I/O Interrupts" described in Section 11.2 of
> > > -"Loongson 3A5000 Processor Reference Manual"; HTVECINTC is "HyperTransport
> > > -Interrupts" described in Section 14.3 of "Loongson 3A5000 Processor Reference
> > > -Manual"; PCH-PIC/PCH-MSI is "Interrupt Controller" described in Section 5 of
> > > -"Loongson 7A1000 Bridge User Manual"; PCH-LPC is "LPC Interrupts" described in
> > > -Section 24.3 of "Loongson 7A1000 Bridge User Manual".
> > > +.. Note::
> > > + - CPUINTC is CSR.ECFG/CSR.ESTAT and its interrupt controller described
> > > + in Section 7.4 of "LoongArch Reference Manual, Vol 1";
> > > + - LIOINTC is "Legacy I/OInterrupts" described in Section 11.1 of
> > > + "Loongson 3A5000 Processor Reference Manual";
> > > + - EIOINTC is "Extended I/O Interrupts" described in Section 11.2 of
> > > + "Loongson 3A5000 Processor Reference Manual";
> > > + - HTVECINTC is "HyperTransport Interrupts" described in Section 14.3 of
> > > + "Loongson 3A5000 Processor Reference Manual";
> > > + - PCH-PIC/PCH-MSI is "Interrupt Controller" described in Section 5 of
> > > + "Loongson 7A1000 Bridge User Manual";
> > > + - PCH-LPC is "LPC Interrupts" described in Section 24.3 of
> > > + "Loongson 7A1000 Bridge User Manual".
And one more thing, is it needed to use a footnote syntax here?
Like:
balabala... CPUINTC [#cpuintc]_
.. [#cpuintc] CPUINTC is CSR.ECFG/CSR.ESTAT and its interrupt controller described in Section 7.4 of "LoongArch Reference Manual, Vol 1";
Thanks,
Wu
next prev parent reply other threads:[~2022-06-17 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:57 [PATCH v3 0/2] docs: Improve loongarch documents Yanteng Si
2022-06-17 10:57 ` [PATCH v3 1/2] docs/LoongArch: Fix notes rendering by using reST directives Yanteng Si
2022-06-17 11:05 ` Huacai Chen
2022-06-17 11:49 ` WANG Xuerui
2022-06-17 12:38 ` YanTeng Si
2022-06-17 12:41 ` Wu XiangCheng [this message]
2022-06-17 10:57 ` [PATCH v3 2/2] docs/zh_CN/LoongArch: " Yanteng Si
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=Yqx2k2V0ap3yD4aF@bobwxc.mipc \
--to=bobwxc@email.cn \
--cc=alexs@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=git@xen0n.name \
--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 \
--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