[jira] [Commented] (MYNEWT-450) Enable extensible module ID and matching names for log messages

["Peter Snyder (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MYNEWT-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589570#comment-15589570 ] 

Peter Snyder commented on MYNEWT-450:
-------------------------------------

There is already a mechanism to associate strings with log messages through the log structure. A way to address this ticket is to add a module ID field to the log structure which is initialized with an additional parameter to the log_register() call. This would simplify generating log messages as the module ID and string are automatically associated with the log and allows for extensibility of log modules as they would be associated with the log structure themselves.

> Enable extensible module ID and matching names for log messages
> ---------------------------------------------------------------
>
>                 Key: MYNEWT-450
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-450
>             Project: Mynewt
>          Issue Type: Improvement
>          Components: OS
>    Affects Versions: v1_0_0_beta1
>            Reporter: Peter Snyder
>            Assignee: Peter Snyder
>
> Log messages are associated with a particular module which can be used for filtering entries. Each module has a string associated with it and this is used by newtmgr to list which log are available.
> While intended to be extensible, there is not a mechanism to associate module strings with additional module types. There are a number of pre-configured module names and strings associated with OS subsystems (e.g, NIMBLE, NFFS, OS...) but a more systematic and extensible way to associate modules and name strings is needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)