[log]Update V5.2.2 Released Changelog. #10877
Conversation
|
👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread! 为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。 🛠 操作步骤 | Steps
完成后，提交将自动更新至 如有问题欢迎联系我们，再次感谢您的贡献！💐 |
There was a problem hiding this comment.
Pull Request Overview
This pull request adds a comprehensive changelog for RT-Thread v5.2.2 release. The document records changes since v5.2.1 across multiple areas including kernel improvements, component updates, BSP additions, and documentation enhancements. Additionally, the PR reformats and corrects indentation issues in previous changelog entries to maintain consistent Markdown formatting throughout the file.
Key Changes
- Addition of complete RT-Thread v5.2.2 release notes documenting kernel fixes, driver updates, new BSP support, and tool improvements
- Reformatting of previous changelog entries (v5.2.1, v5.2.0, v4.1.1, v4.0.4) to fix indentation inconsistencies
- Correction of spacing issues in bullet points and nested list structures throughout the document
ChangeLog.md
Outdated
| * **LWP** | ||
|
|
||
| * Fix potential signal handler infinite loop for riscv. | ||
| * Feat:Restore TP register in arch_thread_signal_enter to fix user-mode memory access. |
There was a problem hiding this comment.
Missing space after colon. English: Add space after 'Feat:' for consistency with other entries. 中文：冒号后缺少空格，应与其他条目保持一致。
| * Feat:Restore TP register in arch_thread_signal_enter to fix user-mode memory access. | |
| * Feat: Restore TP register in arch_thread_signal_enter to fix user-mode memory access. |
ChangeLog.md
Outdated
|
|
||
| ## DM | ||
|
|
||
| * NVME: fix up the QUEUE alloc errorno check. |
There was a problem hiding this comment.
Spelling error in 'errorno'. English: Correct spelling from 'errorno' to 'errno'. 中文：'errorno' 拼写错误，应更正为 'errno'。
| * NVME: fix up the QUEUE alloc errorno check. | |
| * NVME: fix up the QUEUE alloc errno check. |
ChangeLog.md
Outdated
| * the risk for function exit() when open pthread support | ||
| * supplement the case that exit() haven't been impletement | ||
| * try to fix the problem about "fflush" functions in armlibc | ||
| * use ``__clang__`` to replace ``__CLANG_ARM`` |
There was a problem hiding this comment.
Incorrect Markdown code formatting with mismatched backticks. English: Use single backticks for code formatting instead of doubled backticks. 中文：代码格式化使用了错误的反引号，应使用单个反引号而非双重反引号。
| * use ``__clang__`` to replace ``__CLANG_ARM`` | |
| * use `__clang__` to replace `__CLANG_ARM` |
ChangeLog.md
Outdated
| * supplement the case that exit() haven't been impletement | ||
| * try to fix the problem about "fflush" functions in armlibc | ||
| * use ``__clang__`` to replace ``__CLANG_ARM`` | ||
| * solve the compiling error for ``_sys_ensure`` |
There was a problem hiding this comment.
Incorrect Markdown code formatting with mismatched backticks. English: Use single backticks for code formatting instead of doubled backticks. 中文：代码格式化使用了错误的反引号，应使用单个反引号而非双重反引号。
| * solve the compiling error for ``_sys_ensure`` | |
| * solve the compiling error for `_sys_ensure` |
ChangeLog.md
Outdated
| * Add SDIO/EMAC driver for qemu-vexpress-a9 bsp; | ||
| * Enable VC++ to compile simulator bsp; | ||
| * Add stm32f4xx-HAL bsp for kinds of STM32F4 series <User can use menuconfig to select chip>; | ||
| * Add stm32f4xx-HAL bsp for kinds of STM32F4 series `<User can use menuconfig to select chip>`; |
There was a problem hiding this comment.
Inconsistent formatting notation. English: The angle bracket notation inside backticks is unconventional for Markdown. Consider using parentheses or removing backticks. 中文：反引号内的尖括号表示法不符合常规 Markdown 格式，建议使用圆括号或移除反引号。
| * Add stm32f4xx-HAL bsp for kinds of STM32F4 series `<User can use menuconfig to select chip>`; | |
| * Add stm32f4xx-HAL bsp for kinds of STM32F4 series (User can use menuconfig to select chip); |
2 participants
拉取/合并请求描述：(PR description)
[
为什么提交这份PR (why to submit this PR)
你的解决方案是什么 (what is your solution)
请提供验证的bsp和config (provide the config and bsp)
]
当前拉取/合并请求的状态 Intent for your PR
必须选择一项 Choose one (Mandatory):
代码质量 Code Quality：
我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:
#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up