shell / logging: shell log backend output Kconfig #97146
+50
−5
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.
Gives access to all log output format flag configurations for shell backend.
shell log backend doesn't use log_backend_std_get_flags() and it's debateable if it should, so give it its own fullly configurable format set for maximum backend bandwidth control
===================================
There was a little bit of discussion in #94534 about if this should be standard or per-backend and since shell log backend doesn't currently use
log_backend_std_get_flags()
, this was the first approach to narrow the scope of change to only shell's log backend, although I believe all log backends would benefit from having full output format configurability to manage bandwidth traffic.