Skip to content

Conversation

@Yaochenger
Copy link
Contributor

@Yaochenger Yaochenger commented Sep 3, 2024

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

[

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

修正使用rt_device_create创建设备,使用rt_device_destroy删除失败的问题
问题来源:论坛,链接:https://club.rt-thread.org/ask/question/bfbced466a6fd1c0.html

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

在rt_device_unregister后对象类型为RT_Object_Class_Null,将rt_device_destroy中的判断的对象类型改为RT_Object_Class_Null

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

HPM6750 BSP

]

当前拉取/合并请求的状态 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

@github-actions github-actions bot added Kernel PR has src relate code Component labels Sep 3, 2024
@Rbb666 Rbb666 added the bug This PR/issue is a bug in the current code. label Sep 3, 2024
@mysterywolf mysterywolf merged commit 7469edd into RT-Thread:master Sep 3, 2024
@Yaochenger Yaochenger deleted the device branch July 3, 2025 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug This PR/issue is a bug in the current code. Component Kernel PR has src relate code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants