Re: [PR] rpdev_server prefix name enhancement and issue fix [nuttx]

2025-05-06 Thread via GitHub


xiaoxiang781216 commented on PR #16325:
URL: https://github.com/apache/nuttx/pull/16325#issuecomment-2857257385

   @yezhonghui2024 please remove the merge patch


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] rpdev_server prefix name enhancement and issue fix [nuttx]

2025-05-06 Thread via GitHub


yezhonghui2024 closed pull request #16325: rpdev_server prefix name enhancement 
and issue fix
URL: https://github.com/apache/nuttx/pull/16325


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] rpdev_server prefix name enhancement and issue fix [nuttx]

2025-05-06 Thread via GitHub


nuttxpr commented on PR #16325:
URL: https://github.com/apache/nuttx/pull/16325#issuecomment-2854742121

   [**\[Experimental Bot, please feedback 
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
   
   
   
   This PR does **not** appear to meet the NuttX requirements, despite claiming 
to in the Summary.  The provided information is far too vague and lacks crucial 
details.
   
   Here's why:
   
   * **Insufficient Summary:**  "rpdev_servers as base, support many driver 
with prefix name*"  This doesn't explain *why* this change is necessary. What 
problem does it solve? What drivers are being supported?  How does this "prefix 
name" mechanism work?  There are no issue references.
   
   * **Insufficient Impact Assessment:**  "compatibity and enhandce.*" This is 
inadequate.  The PR needs to explicitly state YES/NO for each impact category 
and provide details if YES.  For example, *how* does this affect compatibility? 
 What exactly is enhanced?
   
   * **Missing Testing Information:** The testing section is completely empty.  
There's no information on the build host, target, or any testing logs 
demonstrating the change's functionality.  This is a critical omission.
   
   
   **To meet the requirements, the PR needs to provide the following:**
   
   * **A clear and detailed explanation of the change's purpose and 
functionality in the Summary.**
   * **Complete YES/NO answers for each Impact category with specific 
explanations where necessary.**
   * **Thorough testing information, including build host details, target 
details, and before/after testing logs demonstrating the change's 
effectiveness.**
   * **Links to related issues if applicable.**
   
   
   Without this information, it's impossible to determine if the PR is suitable 
for inclusion in NuttX.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



[PR] rpdev_server prefix name enhancement and issue fix [nuttx]

2025-05-06 Thread via GitHub


yezhonghui2024 opened a new pull request, #16325:
URL: https://github.com/apache/nuttx/pull/16325

   *Note: Please adhere to [Contributing 
Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).*
   
   ## Summary
   
   rpdev_servers as base,  support many driver with prefix name*
   
   ## Impact
   
   compatibity and enhandce.*
   
   ## Testing
   
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]