sched/clock: cleanup g_system_ticks reference if arch timer is enabled

[anchao]

Summary

sched/clock: cleanup g_system_ticks reference if arch timer is enabled

continue work of: #15139

Signed-off-by: chao an [email protected]

Impact

N/A

Testing

ci-check

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not fully meet the NuttX requirements. While it provides a summary and testing information, it lacks crucial details.

Here's a breakdown of what's missing:

• Summary: While it states the what, it omits the why and how. It needs to explain why cleaning up g_system_ticks is necessary when the architecture timer is enabled. What problem does it solve? How does the cleanup work? What code is changed?

• Impact: Simply stating "N/A" is insufficient. Even seemingly minor changes can have unforeseen impacts. Each impact category needs to be explicitly addressed with "NO" or "YES" and a justification. For example, if there's truly no impact on the build, it should say "Impact on build: NO - No changes to the build process." This forces the submitter to consider each potential impact area.

• Testing: "ci-check" is not sufficient. While CI is important, the PR needs to demonstrate local testing. The requirements specifically ask for:

  • Details about the build host and target(s) used for testing.
  • Logs from before the change.
  • Logs from after the change, showing the improvement or fix. Simply saying "ci-check" doesn't provide evidence of the change's effectiveness.

In short, the PR needs more detail and explicit answers to the requirements to be considered complete. The current state makes it difficult to review and understand the full implications of the change.