History log of /openbmc/phosphor-logging/tools/example/xyz/openbmc_project/ (Results 1 – 14 of 14)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
26919f0708-Dec-2022 Patrick Williams <patrick@stwcx.xyz>

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: I6e8d56540a30898369d7f232d900fd74de2e7bd1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...


/openbmc/phosphor-logging/.clang-format
/openbmc/phosphor-logging/.gitignore
/openbmc/phosphor-logging/.lcovrc
/openbmc/phosphor-logging/.shellcheck
/openbmc/phosphor-logging/OWNERS
/openbmc/phosphor-logging/README.md
/openbmc/phosphor-logging/callouts/callout_test.cpp
/openbmc/phosphor-logging/callouts/callouts-gen.mako.hpp
/openbmc/phosphor-logging/callouts/callouts.py
/openbmc/phosphor-logging/config/config.h.meson
/openbmc/phosphor-logging/config/meson.build
/openbmc/phosphor-logging/config_main.h
/openbmc/phosphor-logging/dist/busconfig/phosphor-logging.conf
/openbmc/phosphor-logging/dist/busconfig/phosphor-rsyslog-config.conf
/openbmc/phosphor-logging/dist/meson.build
/openbmc/phosphor-logging/dist/xyz.openbmc_project.Logging.service
/openbmc/phosphor-logging/dist/xyz.openbmc_project.Syslog.Config.service
/openbmc/phosphor-logging/docs/structured-logging.md
/openbmc/phosphor-logging/elog_block.hpp
/openbmc/phosphor-logging/elog_entry.cpp
/openbmc/phosphor-logging/elog_entry.hpp
/openbmc/phosphor-logging/elog_meta.cpp
/openbmc/phosphor-logging/elog_meta.hpp
/openbmc/phosphor-logging/elog_serialize.cpp
/openbmc/phosphor-logging/elog_serialize.hpp
/openbmc/phosphor-logging/extensions.cpp
/openbmc/phosphor-logging/extensions.hpp
/openbmc/phosphor-logging/extensions/meson.build
/openbmc/phosphor-logging/extensions/openpower-pels/README.md
/openbmc/phosphor-logging/extensions/openpower-pels/additional_data.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/ascii_string.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/ascii_string.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/bcd_time.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/bcd_time.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/callout.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/callout.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/callouts.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/callouts.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/data_interface.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/data_interface.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/dbus_types.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/dbus_watcher.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/device_callouts.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/device_callouts.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/entry_points.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/event_logger.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/extended_user_data.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/extended_user_data.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/extended_user_header.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/extended_user_header.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/failing_mtms.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/failing_mtms.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/fapi_data_process.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/fapi_data_process.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/fru_identity.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/fru_identity.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/generic.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/generic.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/host_interface.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/host_notifier.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/host_notifier.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/json_utils.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/json_utils.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/log_id.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/log_id.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/manager.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/manager.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/meson.build
/openbmc/phosphor-logging/extensions/openpower-pels/mru.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/mru.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/mtms.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/mtms.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/paths.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/paths.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pce_identity.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pce_identity.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_entry.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_entry.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_registry/__init__.py
/openbmc/phosphor-logging/extensions/openpower-pels/pel_rules.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_rules.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_types.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_values.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pel_values.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/phal_service_actions.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/phal_service_actions.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/pldm_interface.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/pldm_interface.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/private_header.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/private_header.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/registry.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/registry.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/registry/B_component_ids.json
/openbmc/phosphor-logging/extensions/openpower-pels/registry/O_component_ids.json
/openbmc/phosphor-logging/extensions/openpower-pels/registry/README.md
/openbmc/phosphor-logging/extensions/openpower-pels/registry/message_registry.json
/openbmc/phosphor-logging/extensions/openpower-pels/registry/run-ci.sh
/openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/registry_example.json
/openbmc/phosphor-logging/extensions/openpower-pels/registry/schema/schema.json
/openbmc/phosphor-logging/extensions/openpower-pels/registry/tools/process_registry.py
/openbmc/phosphor-logging/extensions/openpower-pels/repository.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/repository.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/sbe_ffdc_handler.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/sbe_ffdc_handler.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/section.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/section_factory.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/section_factory.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/section_header.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/service_indicators.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/service_indicators.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/setup.py
/openbmc/phosphor-logging/extensions/openpower-pels/severity.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/severity.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/src.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/src.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/stream.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/temporary_file.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/temporary_file.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/tools/peltool.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_data.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_data.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_data_formats.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_data_json.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_data_json.hpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_header.cpp
/openbmc/phosphor-logging/extensions/openpower-pels/user_header.hpp
/openbmc/phosphor-logging/gen/README
/openbmc/phosphor-logging/gen/meson.build
/openbmc/phosphor-logging/gen/regenerate-meson
/openbmc/phosphor-logging/gen/run-ci
/openbmc/phosphor-logging/gen/xyz/meson.build
/openbmc/phosphor-logging/gen/xyz/openbmc_project/Logging/Internal/Manager/meson.build
/openbmc/phosphor-logging/gen/xyz/openbmc_project/Logging/Internal/meson.build
/openbmc/phosphor-logging/gen/xyz/openbmc_project/Logging/meson.build
/openbmc/phosphor-logging/gen/xyz/openbmc_project/meson.build
/openbmc/phosphor-logging/lib/elog.cpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/elog.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/concepts.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/conversion.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/flags.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/header.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/level.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/logger.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/lg2/source_location.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/log.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/meson.build
/openbmc/phosphor-logging/lib/include/phosphor-logging/sdjournal.hpp
/openbmc/phosphor-logging/lib/include/phosphor-logging/test/sdjournal_mock.hpp
/openbmc/phosphor-logging/lib/lg2_logger.cpp
/openbmc/phosphor-logging/lib/meson.build
/openbmc/phosphor-logging/lib/sdjournal.cpp
/openbmc/phosphor-logging/log_manager.cpp
/openbmc/phosphor-logging/log_manager.hpp
/openbmc/phosphor-logging/log_manager_main.cpp
/openbmc/phosphor-logging/logging_test.cpp
/openbmc/phosphor-logging/meson.build
/openbmc/phosphor-logging/meson_options.txt
/openbmc/phosphor-logging/phosphor-rsyslog-config/main.cpp
/openbmc/phosphor-logging/phosphor-rsyslog-config/meson.build
/openbmc/phosphor-logging/phosphor-rsyslog-config/server-conf.cpp
/openbmc/phosphor-logging/phosphor-rsyslog-config/server-conf.hpp
/openbmc/phosphor-logging/phosphor-rsyslog-config/utils.hpp
/openbmc/phosphor-logging/setup.cfg
/openbmc/phosphor-logging/subprojects/CLI11.wrap
/openbmc/phosphor-logging/subprojects/cereal.wrap
/openbmc/phosphor-logging/subprojects/googletest.wrap
/openbmc/phosphor-logging/subprojects/nlohmann-json.wrap
/openbmc/phosphor-logging/subprojects/phosphor-dbus-interfaces.wrap
/openbmc/phosphor-logging/subprojects/pldm.wrap
/openbmc/phosphor-logging/subprojects/sdbusplus.wrap
/openbmc/phosphor-logging/subprojects/sdeventplus.wrap
/openbmc/phosphor-logging/test/common.cpp
/openbmc/phosphor-logging/test/elog_errorwrap_test.cpp
/openbmc/phosphor-logging/test/elog_errorwrap_test.hpp
/openbmc/phosphor-logging/test/elog_quiesce_test.cpp
/openbmc/phosphor-logging/test/elog_update_ts_test.cpp
/openbmc/phosphor-logging/test/extensions_test.cpp
/openbmc/phosphor-logging/test/meson.build
/openbmc/phosphor-logging/test/openpower-pels/additional_data_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/ascii_string_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/bcd_time_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/data_interface_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/device_callouts_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/event_logger_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/extended_user_data_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/extended_user_header_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/failing_mtms_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/fru_identity_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/generic_section_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/host_notifier_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/json_utils_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/log_id_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/meson.build
/openbmc/phosphor-logging/test/openpower-pels/mocks.hpp
/openbmc/phosphor-logging/test/openpower-pels/mru_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/mtms_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/paths.cpp
/openbmc/phosphor-logging/test/openpower-pels/pce_identity_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/pel_manager_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/pel_rules_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/pel_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/pel_utils.cpp
/openbmc/phosphor-logging/test/openpower-pels/pel_utils.hpp
/openbmc/phosphor-logging/test/openpower-pels/pel_values_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/private_header_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/real_pel_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/registry_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/repository_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/section_header_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/service_indicators_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/severity_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/src_callout_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/src_callouts_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/src_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/stream_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/temporary_file_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/user_data_test.cpp
/openbmc/phosphor-logging/test/openpower-pels/user_header_test.cpp
/openbmc/phosphor-logging/test/remote_logging_test_address.cpp
/openbmc/phosphor-logging/test/remote_logging_test_config.cpp
/openbmc/phosphor-logging/test/remote_logging_test_port.cpp
/openbmc/phosphor-logging/test/remote_logging_tests.hpp
/openbmc/phosphor-logging/test/sdtest.cpp
/openbmc/phosphor-logging/test/serialization_test_path.cpp
/openbmc/phosphor-logging/test/serialization_test_properties.cpp
/openbmc/phosphor-logging/test/serialization_tests.hpp
/openbmc/phosphor-logging/tools/elog-gen.py
Example/Bar.metadata.yaml
Example/Device.metadata.yaml
Example/Elog.metadata.yaml
Example/Foo.metadata.yaml
/openbmc/phosphor-logging/tools/meson.build
/openbmc/phosphor-logging/tools/phosphor-logging/templates/elog-gen-template.mako.hpp
/openbmc/phosphor-logging/tools/phosphor-logging/templates/elog-lookup-template.mako.cpp
/openbmc/phosphor-logging/tools/phosphor-logging/templates/elog-process-metadata.mako.cpp
/openbmc/phosphor-logging/tools/phosphor-logging/templates/meson.build
/openbmc/phosphor-logging/util.cpp
/openbmc/phosphor-logging/util.hpp
/openbmc/phosphor-logging/yaml/xyz/openbmc_project/Logging/Internal/Manager.interface.yaml
739e925605-Mar-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

test: add callout-test

Add test program which can create callouts based on an input device
path. It creates an error, with callouts, with name TestCallout.

Change-Id: I96b66b73ae4a9c00daff06222841a

test: add callout-test

Add test program which can create callouts based on an input device
path. It creates an error, with callouts, with name TestCallout.

Change-Id: I96b66b73ae4a9c00daff06222841a13747c07408
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

89d6be4127-Feb-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

metadata: introduce 'process' keyword

An error metadata field that has the 'process' keyword set to true is
an indication that this metadata will have some associated action that
will take place aft

metadata: introduce 'process' keyword

An error metadata field that has the 'process' keyword set to true is
an indication that this metadata will have some associated action that
will take place after this metadata (and associated error) is logged to
the journal and before the associated error is committed.

The associated action will have to be implemented when adding the
'process' keyword.

Add 'process' keyword to an example error definition.

Change-Id: I42ab3fa230479000a88a18046548242c0043ac86
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

e0eb1ddd19-Feb-2017 Michael Tritz <mtritz@us.ibm.com>

Error log inject tool

This tool adds an option to the logging-test
to inject an error as specified by command
line.

Change-Id: I1028bd3964db23ed5ffa50414f7a6cc2f880c40c
Signed-off-by: Michael Tritz

Error log inject tool

This tool adds an option to the logging-test
to inject an error as specified by command
line.

Change-Id: I1028bd3964db23ed5ffa50414f7a6cc2f880c40c
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>

show more ...

465aaecc20-Feb-2017 Adriana Kobylak <anoo@us.ibm.com>

Include namespaces in the phosphor-logging exception name

Currently the phosphor-logging exception name is for example
Device for an error file located in xyz/openbmc_project/Error/Callout/.
It shou

Include namespaces in the phosphor-logging exception name

Currently the phosphor-logging exception name is for example
Device for an error file located in xyz/openbmc_project/Error/Callout/.
It should instead be named xyz.openbmc_project.Error.Callout.Device
following the naming structure of the sdbusplus++ tool
to differentiate it from other Device error exceptions.
With the full name, the namespaces can be determined, so there's no
need to pass the namespace parameter to the template that generates
the elog-errors.hpp. As with the name, follow the namespace
structure of the sdbusplus exception object.

Closes openbmc/phosphor-logging#2

Change-Id: I960d759d90aa18fd43211034ebd6009859113ee7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>

show more ...

17944e1313-Feb-2017 Adriana Kobylak <anoo@us.ibm.com>

Move inherits keyword from errors.yaml to metadata.yaml

The metadata.yaml file is the correct location for the inherits.
Update the elog-gen.py parser to support this change.

Change-Id: Iac7f67ec72

Move inherits keyword from errors.yaml to metadata.yaml

The metadata.yaml file is the correct location for the inherits.
Update the elog-gen.py parser to support this change.

Change-Id: Iac7f67ec72e761ab3dafbf89c7e4d5495b34f00d
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>

show more ...

5d1aace618-Jan-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

elog-gen.py : order inherited errors

The elog-gen.py script should process errors such that the generated
code has definitions for parent errors before their child errors are
defined.

Change-Id: I0

elog-gen.py : order inherited errors

The elog-gen.py script should process errors such that the generated
code has definitions for parent errors before their child errors are
defined.

Change-Id: I035292731346bdba969f549c7e4033066814890f
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

82b7de7e17-Jan-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

elog-gen.py : get inherited-from error

Openbmc error interfaces can inherit other error interfaces, thereby
allowing to combine metadata across errors. The current implementation
would support singl

elog-gen.py : get inherited-from error

Openbmc error interfaces can inherit other error interfaces, thereby
allowing to combine metadata across errors. The current implementation
would support single inheritance only.

This first commit related to error inheritance implementation lets
elog-gen.py figure out an error's parent.

Change-Id: Ia5c44de755e777e0cb2725afa5988c97283d10f0
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

160d3e0b17-Jan-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

elog-gen.py : read multiple error yaml files

This change enables the elog-gen script to look at more than one error
yaml file (and corresponding metadata yaml file). The input to the
script had to b

elog-gen.py : read multiple error yaml files

This change enables the elog-gen script to look at more than one error
yaml file (and corresponding metadata yaml file). The input to the
script had to be changed to a yaml directory, containing
error yaml files, instead of a single error yaml file.

The reason to support reading multiple error yaml files is that,
without this, applications have to all dump their errors in a single big
error yaml file. Now it's possible to write application/domain specific
error yaml files; they just need to be exported to the same location,
from where elog-gen.py can pick them.

Change-Id: I9418bf0e0b54a7b7f7701b337649cb8eb4c54913
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

9916119f16-Jan-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

Fix types in error-logging YAML to match openbmc standards

Change-Id: If5e2e534740f0675ba9294905ae531e015aed85a
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

d310378f16-Jan-2017 Deepak Kodihalli <dkodihal@in.ibm.com>

Rename <Interface>.logging.yaml to <Interface>.metadata.yaml

This change is just for brevity.

Change-Id: Ie2360b19179837a1dc3675e96a4adcc2114f2bc6
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.c

Rename <Interface>.logging.yaml to <Interface>.metadata.yaml

This change is just for brevity.

Change-Id: Ie2360b19179837a1dc3675e96a4adcc2114f2bc6
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>

show more ...

e859630021-Nov-2016 Andrew Geissler <andrewg@us.ibm.com>

Break elog yaml files into two pieces

This is the final piece to supporting the phosphor-dbus-interfaces
design where the errors are defined in one yaml file and
their corresponding meta data is def

Break elog yaml files into two pieces

This is the final piece to supporting the phosphor-dbus-interfaces
design where the errors are defined in one yaml file and
their corresponding meta data is defined within another file.

Change-Id: Idd2e18c1fd82fccb1298a2570a484deb382954f8
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>

show more ...

f1f2cfa921-Nov-2016 Andrew Geissler <andrewg@us.ibm.com>

Base error log namespaces on yaml file path

This is another step in the direction of getting us
to support the error yaml file as it will be
defined in the phosphor-dbus-interfaces repo.

Change-Id:

Base error log namespaces on yaml file path

This is another step in the direction of getting us
to support the error yaml file as it will be
defined in the phosphor-dbus-interfaces repo.

Change-Id: Ib437bea920f511bdbf541c3e2653bbf35a83fe92
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>

show more ...

33ff62a221-Nov-2016 Andrew Geissler <andrewg@us.ibm.com>

Move the phosphor logging example yaml into sub directory

The real yaml will be defined in the phosphor-dbus-interfaces
repo. This one will be an example one and used for testing.
Future commits wi

Move the phosphor logging example yaml into sub directory

The real yaml will be defined in the phosphor-dbus-interfaces
repo. This one will be an example one and used for testing.
Future commits will refactor it to separate the error def
from the meta data.

Change-Id: Id05f935cbc24fb030e2ba378423ef3261bf5f7fb
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>

show more ...