Clarify tasklet limitations and deprecation plans #306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Improve wording and grammar in the tasklet section. Reflect current discussion on tasklet deprecation and correct Linux kernel casing.
|
Thank @EricccTaiwan for contributing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve wording and grammar in the tasklet section. Reflect current discussion on tasklet deprecation and correct Linux kernel casing.
Summary by Bito
This pull request enhances the documentation for tasklets in the Linux kernel, clarifying their limitations and addressing discussions on potential deprecation. It also corrects the casing of 'Linux' for consistency throughout the document.Unit tests added: False
Estimated effort to review (1-5, lower is better): 2