[PR] socketpair.c:Replace kmm with fs heap [nuttx]

["wangchen61698 (via GitHub)" <gi...@apache.org>]

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

   
   ## Summary
   
   due to https://github.com/apache/nuttx/pull/13722/commits, In the socketpair.c,fs_heap interface replaces kmm interface
   
   ## Impact
   
   sockpair
   
   ## Testing
   
   Manual verification
   
   


-- 
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-unsubscribe@nuttx.apache.org

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

Re: [PR] socketpair.c:Replace kmm with fs heap [nuttx]

["nuttxpr (via GitHub)" <gi...@apache.org>]

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

   [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
   
   
   
   **No, this PR does not meet the NuttX Requirements.**
   
   Here's why and how to fix it:
   
   **Missing Information in Summary:**
   
   * **Why is the change necessary?**  Simply stating that one interface replaces another isn't enough. Explain the problem with the old `kmm` interface and why `fs_heap` is a better solution.
   * **What functional part of the code is being changed?**  Be specific.  Mention the affected files (e.g., `socketpair.c`) and the specific functions within those files.
   * **How does the change exactly work?**  Provide a technical explanation of the changes made to transition from `kmm` to `fs_heap`.
   
   **Insufficient Impact Assessment:**
   
   * **Impact on user:**  Does this change affect how users interact with socket pairs? If so, how?
   * **Impact on build, hardware, documentation, security, compatibility:**  Address all these points. Even if the answer is "NO," state it explicitly. 
   
   **Lack of Testing Details:**
   
   * **Build Hosts:** List the specific operating systems, CPUs, and compiler versions used for testing.
   * **Targets:**  Specify the architectures (e.g., x86, ARM) and boards used. 
   * **Testing Logs:**  The provided logs are placeholders. Include actual logs showing the behavior of the code before and after your changes.
   
   **How to Improve the PR:**
   
   1. **Expand the Summary:** Provide a clear and concise explanation of the problem, the solution, and the technical details of the change.
   2. **Complete the Impact Assessment:** Thoroughly address all impact categories, even if they are not affected.
   3. **Provide Detailed Testing Information:** Include specific build environments, target platforms, and relevant testing logs.
   
   By providing this missing information, you'll make it much easier for reviewers to understand and approve your PR. 
   


-- 
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-unsubscribe@nuttx.apache.org

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

Re: [PR] socketpair.c:Replace kmm with fs heap [nuttx]

["GUIDINGLI (via GitHub)" <gi...@apache.org>]

GUIDINGLI merged PR #14346:
URL: https://github.com/apache/nuttx/pull/14346


-- 
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-unsubscribe@nuttx.apache.org

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