[Rbb666]

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

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

将 RT-Thread 版本从 5.3.1 更新为 5.4.0，并保持内核版本定义与 Kconfig 版本数值一致。
Bump RT-Thread from 5.3.1 to 5.4.0 and keep the kernel and Kconfig version definitions consistent.

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

• include/rtdef.h: 将版本宏设为 5.4.0，并添加变更记录。Set the version macros to 5.4.0 and add a changelog entry.
• src/Kconfig: 将 RT_VER_NUM 默认值设为 0x50400。Set the default RT_VER_NUM to 0x50400.

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

• BSP: bsp/qemu-vexpress-a9.
• .config: 基于默认配置运行 scons --pyconfig-silent，确认生成的配置和 rtconfig.h 中 RT_VER_NUM=0x50400。Regenerated the default configuration and verified RT_VER_NUM=0x50400.
• 本地验证 / Local validation: scons -j8 编译成功；QEMU 启动显示 5.4.0 build ... 并进入 msh />。The build passed; QEMU printed version 5.4.0 and reached the shell.
• QEMU 使用无显示模式、未挂载 SD 卡；声音设备和 SD 挂载提示不影响上述启动验证。QEMU ran headless without an SD image; host audio and SD mount warnings did not prevent the boot check.
• git diff --check 通过。Passed.
• action: 本次使用本地构建与 QEMU 验证，无独立的 fork Actions 验证链接。Validated locally; no separate fork Actions validation link.

当前拉取/合并请求的状态 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
• 已经使用clang-format 源码格式化工具确保格式符合RT-Thread代码规范 This PR has been formatted with clang-format and complies with RT-Thread code specification
• 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

[github-actions]

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

---

🛠 操作步骤 | Steps

1. 前往 Actions 页面 | Go to the Actions page
   点击进入工作流 → | Click to open workflow →

2. 点击 Run workflow | Click Run workflow

• Use workflow from 保持默认分支（通常为 master）
  Keep the default branch (usually master) in Use workflow from
• 在 branch 输入框填写 PR 分支 bump-version-5.4.0
  Enter PR branch bump-version-5.4.0 in the branch field
• 设置需排除的文件/目录（目录请以"/"结尾）
  Set files/directories to exclude (directories should end with "/")

3. 等待工作流完成 | Wait for the workflow to complete
   格式化后的代码将作为独立提交推送至你的分支。
   The formatting changes will be pushed to your branch as a separate commit.

完成后，提交将自动更新至 bump-version-5.4.0 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the bump-version-5.4.0 branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

[github-actions]

📌 Code Review Assignment

🏷️ Tag: kernel

Reviewers: @GorrayLi @ReviewSun @hamburger-os @lianux-mm @wdfk-prog @xu18838022837

Changed Files (Click to expand)

• src/Kconfig

---

📊 Current Review Status (Last Updated: 2026-10-17 09:35 CST)

• ⌛ @GorrayLi Pending Review
• ⌛ @ReviewSun Pending Review
• ⌛ @hamburger-os Pending Review
• ⌛ @lianux-mm Pending Review
• ⌛ @wdfk-prog Pending Review
• ⌛ @xu18838022837 Pending Review

---

📝 Review Instructions

1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
   Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

2. 确认审核通过后评论 LGTM/lgtm
   Comment LGTM/lgtm after confirming approval

3. PR合并前需至少一位维护者确认
   PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

[github-actions]

MemBrowse Memory Report

No memory changes detected for:

• at32f415-start
• esp32-c3
• gd32105r-start
• hc32f334
• hpmicro-hpm5301evklite
• infineon-psoc6
• k230
• loongson-ls1cdev
• nordic-nrf51822
• nuvoton-m487
• nxp-lpc1114
• qemu-virt64-aarch64
• raspberry-pico-rp2040
• renesas-ra2l1
• simulator
• stm32f407-rt-spark
• stm32l475-atk-pandora-llvm
• wch-ch32v208w-r0
• x86
• xuantie-e901plus

[usualtreee]

Verification of v5.4.0 version bump on QEMU vexpress-a9

Environment:

• WSL Ubuntu, arm-none-eabi-gcc, QEMU vexpress-a9
• Latest master (commit after [kernel] Bump version to v5.4.0 #11875 merged)

1. Version macro check ✓

• include/rtdef.h: RT_VERSION_MAJOR=5, MINOR=4, PATCH=0 -> 5.4.0
• src/Kconfig: RT_VER_NUM = 0x50400
• Two places are consistent.

2. Build & run on QEMU ✓

• scons -j4 build succeeded on bsp/qemu-vexpress-a9
• Booted with ./qemu-nographic.sh, msh works normally
• version command output:
  \ | /
• RT - Thread Operating System
  / | \ 5.4.0 build Oct 17 2026
  2006 - 2026 Copyright by RT-Thread team

3. Residual check (minor findings)
Searched for 5.3.1 and 0x50301 across the repo. Found:

• 6 BSP rtconfig.h files still have RT_VER_NUM 0x50301 (expected - these are generated per-BSP and will update when maintainers re-run menuconfig):
  • bsp/n32/n32hxxx/n32h497zgl7-evb, n32h760zil7-stb, n32h487zgl7-evb
  • bsp/renesas/ra6w1-ek
  • bsp/wch/risc-v/ch32v003f4p6-evt, ch32v203c-evt-r0
• bsp/stm32/stm32n657-st-nucleo/README.md and README_zh.md still show 5.3.1 in the example banner output (line 221).
• CMSIS library version V5.3.1 and doc section number 5.3.1 are unrelated to RT-Thread version.

Conclusion: Core version bump is correct and verified on QEMU. The residual rtconfig.h entries are expected per-BSP artifacts; the README example in stm32n657-st-nucleo could be updated by that BSP maintainer.

[Rbb666]

• BSP rtconfig.h

It's normal for rtconfig.h to remain in the BSP; it will be refreshed via a script during version release.