examples:spislave_test: Improve example

[FelipeMdeO]

Improve example, now it can receive data from user

Summary

Spislv example was improved. Now it can receive data from user. It follow spitool features standard:
This changes was done in parallel at apache/nuttx#14642. Both are tested together .

Impact

No Impact

Testing

This changes was done in parallel at apache/nuttx#14642. Both are tested together .

[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 the missing information:

• Summary: While it explains the "what," it lacks sufficient detail on the "how." It mentions following spitool features but doesn't explain which features or how they were implemented. The reference to a parallel PR is helpful, but the description should stand on its own. What specific files were changed in the spislv example?

• Impact: Simply stating "No Impact" is insufficient. Each impact category should be addressed individually, even if the answer is "NO." For example:

  • Impact on user: NO
  • Impact on build: NO
  • ...and so on for all categories. This demonstrates that each aspect has been considered.

• Testing: While it mentions testing with a parallel PR, the logs are missing. "Both are tested together" isn't enough. Provide specific logs showing the behavior before and after the change in this PR. Include the specific build host and target details. What OS, architecture, board, and configuration were used for testing?

In short: The PR needs more details in the Summary, explicitly address each Impact category, and include actual testing logs with specific host/target information. Relying on a parallel PR for context isn't sufficient for a thorough review.

[cederom]

Thank you @FelipeMdeO :-) Please fix code formatting, see: https://github.com/apache/nuttx-apps/actions/runs/11673965696/job/32505715960?pr=2820

[acassis]

@FelipeMdeO the coding style issues are just Long Lines, you can use the tools/checkpatch.sh -f path/to/file.c/h to show the lines with issues

[cederom]

ping :-)