Allow GPIO example built with Linux v6.10+

[jeremy90307]

gpio_request_array() and gpio_free_array() were
removed in Kernel v6.10-rc1. Use gpio_request()
and gpio_free() instead to make the example run
successfully on v6.10+.

[jserv]

Use preprocessor directives for the compatibility among several Linux kernel versions.

[jeremy90307]

I understand. I will fix it by using preprocessor directives.

[jserv]

I understand. I will fix it by using preprocessor directives.

Ensure that LKM can be built with Linux v5.15, v6.1, and v6.6+.

[jserv]

Mention in git commit messages rather than program comments.

[jserv]

You should denote the commit hash associated with the removal of gpio_request_array and gpio_free_array.

[jeremy90307]

I have removed this comment and mentioned it in the commit message.

[jserv]

No, always squash and refine the messages.

[jserv]

Read https://cbea.ms/git-commit/ carefully and enforce the rules. You should refine the git commit messages.

[jserv]

I have removed this comment and mentioned it in the commit message.

You must refer to the exact git commit hash and summarize the rationale.

[jserv]

Fix conflicts and use git rebase -i to squash commits.

[jserv]

Read https://cbea.ms/git-commit/ carefully and enforce the rules.

[jeremy90307]

Thank you, I will make the necessary corrections.

[jserv]

Thank you, I will make the necessary corrections.

Demonstrate your solution through concrete actions rather than making verbal promises.

[jeremy90307]

Is there anything to improve in this commit? Thank you.

[jserv]

Is there anything to improve in this commit?

Carefully study the principles of https://cbea.ms/git-commit/ . When writing a commit message, use the imperative mood in the subject line, specifically employing precise action verbs. For instance, use "Allow" rather than passive constructions.
Ensure your commit message body is wrapped at 72 characters without cutting off words mid-line. More critically, focus on explaining the what and why of your changes, not the how. The message should provide substantive context about the rationale behind the code modification.

Take commit d2d54ca for example. We prefer the notation commit b8780c363d80 ("sched: remove sleep_on() and friends"). This format is preferred because it concisely combines the commit hash with a descriptive subject line. The message should go beyond mere description and dive into the underlying reasoning for the change.

When contributing to a technical project, communication should be direct and purposeful. The phrase "Thank you" becomes unnecessary when the primary goal is collaborative technical work. In a professional development context, your interactions should focus on the technical details, code quality, and project improvement.

[jserv]

Compose Git commit messages in the third person, and include a test summary specific to Raspberry Pi deployment or testing.

[jserv]

Refine the git commit message as following:

Commit dbcedec ("gpiolib: legacy: Remove unused gpio_request_array()
and gpio_free_array()") indicated that there are no more users of these
functions; therefore, they were removed.

And address the considerations of removal fro Linux kernel developers' perspectives.

[jeremy90307]

https://github.com/user-attachments/assets/bc43c25b-f02a-43c7-9bd1-a178f94b99f5
Successfully ran on Linux v6.12.1.

[jserv]

https://github.com/user-attachments/assets/bc43c25b-f02a-43c7-9bd1-a178f94b99f5 Successfully ran on Linux v6.12.1.

You should explain the testing procedure within git commit messages as well.

[jeremy90307]

My testing steps only include compiling, connecting an LED and a button, and finally loading the module.

[jserv]

Rebase the latest master branch to pass CI pipeline.

[jserv]

Replace Resolves:#285 with shorter Close #285.

[jserv]

Thank @jeremy90307 for contributing!