libc: add missing preadv/pwritev in CMakeLists.txt

[yamt]

Summary

Impact

Testing

[lupyuen]

[Experimental Bot, please feedback here]

This appears to be a template or checklist for creating good Pull Requests (PR) for the NuttX operating system. It's not a PR itself, but instructions to follow before submitting a PR.

Here's a breakdown of what each section wants you to fill out:

## Summary

This section ensures you clearly communicate the "what" and "why" of your code changes:

• Purpose: Explain the reason behind your changes: bug fix, new feature, update, etc.
• Scope: Specify the part of the codebase affected by your changes.
• Functionality: Describe how your code works and how it modifies the existing behavior.
• Related Issues: Link to relevant issues on NuttX's GitHub repository to provide context and traceability.

## Impact

This section assesses the potential consequences of your changes on different aspects of NuttX:

• Feature Changes: Note if you are adding a new feature or modifying an existing one.
• User Impact: Will users need to adjust their usage or configurations because of your changes?
• Build Process Impact: Do your changes affect how NuttX is built?
• Hardware Impact: Are there any changes to supported hardware architectures, boards, or drivers?
• Documentation Impact: Does your PR require updates or additions to NuttX's documentation?
• Security Impact: Do your changes introduce any potential security vulnerabilities or enhancements?
• Compatibility Impact: Will your changes affect backward compatibility, forward compatibility, or interoperability?
• Other Considerations: Mention any other relevant impacts not covered above.

## Testing

This section demonstrates that you have thoroughly tested your changes:

• Testing Environments: List the details of your build host and target environments (OS, CPU, compiler, architecture, board, configuration, etc.).
• Testing Logs: Provide logs showing the behavior of the relevant functionality before and after your changes. This evidence helps reviewers understand the impact and verify the correctness of your changes.

In short, this template guides contributors to create well-documented and thoroughly tested PRs, which helps maintain the quality and stability of the NuttX project.

[jerpelea]

this commit misses the commit message explaining the change. please fill it

[xiaoxiang781216]

The commit message already explains the change enough, why do we need add some many unnecessary information? is it good to apply this rigid requirement for all patch?