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

   [**\[Experimental Bot, please feedback 
here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
   
   
   
   No, this PR does not fully meet the NuttX requirements.  While it provides a 
summary of the *what*, it lacks sufficient detail on the *why* and *how*.  The 
Impact and Testing sections are also severely lacking.
   
   Here's a breakdown of what's missing:
   
   * **Summary:**
       * **Missing "Why":**  Why is replacing the critical section with a small 
lock necessary? What problem does it solve?  Performance improvement?  Deadlock 
avoidance?  Explain the rationale.
       * **Missing "How":** What specific changes were made to the code to 
implement the small lock? Which lock is used? How does this interact with other 
locking mechanisms?
   
   * **Impact:**
       * **Insufficient Detail:** Simply stating "sched_processtimer" is not 
enough.  Address *all* the impact points.  At minimum, explain if this impacts 
users, the build, hardware, documentation, security, or compatibility.  Even if 
the answer is "NO" for each, explicitly state it.  For example: "Impact on 
user: NO".
   
   * **Testing:**
       * **Insufficient Detail:**  "ci ostest" is not sufficient.  Provide 
specifics:
           * **Build Host(s):** What operating system, CPU architecture, and 
compiler version were used for building?
           * **Target(s):**  What architecture and board/configuration were 
used for testing?  Was this tested on a simulator or real hardware?
           * **Logs:**  The provided log sections are empty. Include *actual* 
logs demonstrating the behavior before and after the change.  Show how the 
change addresses the problem described in the "Why" section of the summary.
   
   In short, the PR needs significantly more detail to be considered complete.  
It needs to clearly explain the motivation, implementation, and testing of the 
change.
   


-- 
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: commits-unsubscr...@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to