Skip to content

doxygen: update doc for kenrel object model #10104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 12, 2025

Conversation

unicornx
Copy link
Contributor

将 markdown 中对函数的参数的介绍移到源码注释中,因为这部分内容完全是重复的,我们只要保留并维护代码中的注释即可,markdown 中涉及 API 的详细解释可以直接引用代码中的注释。

尽量不在 markdown 文档中直接复制结构体的定义,因为这部分内容可能随着代码的升级而发生改动,所以 markdown 中涉及结构体定义时尽量注明这只是代码片段,具体的定义还是直接引用源码以及源码的注释。

markdown 中引用结构体和函数非常方便,只要用 “`" 将结构体名字或者函数名字括起来,生成的 html 就是指向其定义的链接。

按照这个原则,本补丁只是修改了 kernel object model 部分的文档和代码注释。其他模块以后另外提补丁逐个修改。

拉取/合并请求描述:(PR description)

[

为什么提交这份PR (why to submit this PR)

见 PR 描述。

你的解决方案是什么 (what is your solution)

请提供验证的bsp和config (provide the config and bsp)

  • BSP:
  • .config:
  • action:

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

  • 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
  • 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality:

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

  • 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
  • 代码风格正确,包括缩进空格,命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
  • 没有垃圾代码,代码尽量精简,不包含#if 0代码,不包含已经被注释了的代码 All redundant code is removed and cleaned up
  • 所有变更均有原因及合理的,并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
  • 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
  • 代码是高质量的 Code in this PR is of high quality
  • 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification
  • 如果是新增bsp, 已经添加ci检查到.github/workflows/bsp_buildings.yml 详细请参考链接BSP自查

Move the introduction of function parameters in markdown to
source code comments, because this part of the content is
completely repeated. We only need to keep and maintain the
comments in the code. The detailed explanation of the API
in markdown can directly refer to the comments in the code.

Try not to directly copy the definition of the structure
in the markdown document, because this part of the content
may change with the upgrade of the code. Therefore, when
the structure definition is involved in markdown, try to
indicate that it is just a code snippet. The specific
definition is still directly quoted from the source code
and the source code comments.

It is very convenient to quote structures and functions
in markdown. Just use "`" to enclose the structure name
or function name, and the generated html is a link to
its definition.

According to this principle, this patch only modifies
the documents and code comments of the kernel object model.
Other modules will be modified one by one in separate
patches later.

Signed-off-by: Chen Wang <[email protected]>
@github-actions github-actions bot added Doc This PR/issue related with documents Kernel PR has src relate code labels Mar 12, 2025
@unicornx unicornx requested a review from Rbb666 March 12, 2025 03:11
@unicornx
Copy link
Contributor Author

@1078249029 有空请看一下,以后 driver 那边的文档改进也可以参考这个原则进行。

@Rbb666 Rbb666 merged commit 5a42cfd into RT-Thread:master Mar 12, 2025
55 checks passed
@unicornx unicornx deleted the dev-doxygen-kernel-object-model branch March 12, 2025 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Doc This PR/issue related with documents Kernel PR has src relate code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants