usb: device_next: cdc_acm: set the thread name after initializing it #83364
+1
−2
Conversation
This file contains 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
The cdc-acm workqueue thread name is set before initializing it right now, which results in an empty thread name as apparently it gets cleared by k_work_queue_init. Fix it by moving the thread name setting after the workqueu is initialized and started. Signed-off-by: Fabio Baltieri <[email protected]>
fabiobaltieri
added
the
Trivial
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cdc-acm workqueue thread name is set before initializing it right now, which results in an empty thread name as apparently it gets cleared by k_work_queue_init. Fix it by moving the thread name setting after the workqueu is initialized and started.