You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@mynewt.apache.org by "Sheela (JIRA)" <ji...@apache.org> on 2017/06/05 18:56:04 UTC

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

     [ https://issues.apache.org/jira/browse/MYNEWT-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheela resolved MYNEWT-450.
---------------------------
    Resolution: Fixed

> 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
>      Security Level: Public(Viewable by anyone) 
>          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.15#6346)