nuttx/syscall: export nxsem_getprioceiling and nxsem_setprioceiling v…

[ThePassionate]

Summary

1. fix compilation errors when compiling priority protection interfaces in protected mode with pthread_mutex_setprioceiling and pthread_mutex_getprioceiling
2. can use the default lock even in priority protect mode

Impact

compile & ltp

Testing

ci

[nuttxpr]

[Experimental Bot, please feedback here]

This PR appears to be missing some required information.

Here's a breakdown:

What's Good:

• Summary: Provides a brief description of the issue and the proposed solution.
• Testing: Mentions "ci", indicating Continuous Integration testing is expected.

What Needs Improvement:

• Summary:
  • Lacks specificity about the functional code changes. Phrases like "compilation errors" and "use the default lock" are vague.
  • Missing related issue references (if applicable).
• Impact:
  • Overly brief. "compile & ltp" doesn't explain the impact clearly.
  • Needs to address all impact points with "YES/NO" and explanations. For example:
    • Is new feature added? Likely NO (since it's a fix)
    • Is existing feature changed? Likely YES (since a fix implies a change) - provide details.
    • Impact on user: Explain how the fix might affect users.
    • Impact on build: If the fix affects the build process, describe how.
    • ...and so on for all impact points.
• Testing:
  • "ci" is not sufficient. While CI is good, the PR should include:
    • Specific build host details (OS, CPU, compiler).
    • Specific target details (architecture, board, configuration).
    • Relevant testing logs from before and after the change to demonstrate the fix.

Recommendation:

Expand on the missing information to meet the NuttX PR requirements fully. Providing clear and detailed information ensures reviewers can understand the changes and their implications effectively.