From: Alex Shi <seakeel@gmail.com>
To: yanteng si <siyanteng01@gmail.com>
Cc: Yanteng Si <siyanteng@loongson.cn>,
Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-doc@vger.kernel.org, Puyu Wang <realpuyuwang@gmail.com>,
Wu XiangCheng <bobwxc@email.cn>,
huangjianghui@uniontech.com
Subject: Re: [PATCH v6 1/3] docs/zh_CN: add core-api kernel-api.rst translation
Date: Mon, 17 May 2021 11:20:55 +0800 [thread overview]
Message-ID: <e371a1e6-d38d-f5fc-1ad6-1aee116da468@gmail.com> (raw)
In-Reply-To: <CAEensMydFLpmUaCHUYwQ7d_WR+HDbPboTdMAOA+H+FUqcaur_g@mail.gmail.com>
On 2021/5/17 上午9:55, yanteng si wrote:
> Alex Shi <seakeel@gmail.com> 于2021年5月16日周日 上午11:30写道：
>>
>>
>>
>> On 2021/5/15 下午4:10, Yanteng Si wrote:
>>
>>> +安全框架
>>> +========
>>> +
>>> +check the functions in security/security.c in kernel source code.
>>> + :internal:
>>> +
>>> +check the functions in security/inode.c in kernel source code.
>>> + :export:
>>> +
>>> +审计接口
>>> +========
>>> +
>>> +check the functions in kernel/audit.c in kernel source code.
>>> + :export:
>>> +
>>> +check the functions in kernel/auditsc.c in kernel source code.
>>> + :internal:
>>> +
>>> +check the functions in kernel/auditfilter.c in kernel source code.
>>> + :internal:
>>> +
>>
>> Too verbose w/o much useful info, Is the following better?
>>
>> APIs in kernel code: kernel/audit.c, kernel/auitsc.c and kernel/auditfilter.c
>>
>> 该 APIs 在以下内核代码中 kernel/audit.c, kernel/auitsc.c and kernel/auditfilter.c
> It looks great, but in some cases, sentences that are too long have
> some difficulty with a new line, and they are not neat after the new
> line.
> For example::
>
> 这些函数在以下内核代码中 include/asm-generic/bitops/instrumented-atomic.h，
> include/asm-generic/bitops/instrumented-non-atomic.h and
> include/asm-generic/bitops/instrumented-lock.h
> ...
>
> how about::
>
> 该API在以下内核代码中:
>
> kernel/audit.c
> kernel/auitsc.c
> kernel/auditfilter.c
>
> 该API在以下内核代码中:
>
> include/asm-generic/bitops/instrumented-atomic.h
> include/asm-generic/bitops/instrumented-non-atomic.h
> include/asm-generic/bitops/instrumented-lock.h
Right split them into multiple lines looks better.
> ?
>
> Thanks,
> Yanteng
>
next prev parent reply other threads:[~2021-05-17 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 8:10 [PATCH v6 0/3] docs/zh_CN add three core api docs Yanteng Si
2021-05-15 8:10 ` [PATCH v6 1/3] docs/zh_CN: add core-api kernel-api.rst translation Yanteng Si
2021-05-16 3:30 ` Alex Shi
2021-05-17 1:55 ` yanteng si
2021-05-17 3:20 ` Alex Shi [this message]
2021-05-17 8:17 ` yanteng si
2021-05-16 11:37 ` Jiaxun Yang
2021-05-17 2:33 ` yanteng si
2021-05-15 8:10 ` [PATCH v6 2/3] docs/zh_CN: add core-api printk-basics.rst translation Yanteng Si
2021-05-16 11:38 ` Jiaxun Yang
2021-05-17 2:47 ` yanteng si
2021-05-15 8:10 ` [PATCH v6 3/3] docs/zh_CN: add core-api printk-formats.rst translation Yanteng Si
2021-05-16 11:40 ` Jiaxun Yang
2021-05-17 2:41 ` 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=e371a1e6-d38d-f5fc-1ad6-1aee116da468@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=huangjianghui@uniontech.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=realpuyuwang@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;
as well as URLs for NNTP newsgroup(s).