/openbmc/phosphor-objmgr/libmapper/ |
H A D | mapper.h | d0cf9428 Tue Sep 17 03:01:34 CDT 2019 John Wang <wangzqbj@inspur.com> Drop support for old association interface A new association interface is defined in phosphor-dbus-interfaces It would be nice to move the local version of the interface to the new one. The behavior of how association work is described here: https://github.com/openbmc/docs/blob/master/object-mapper.md#associations I did some searching and confirmed that all the old interfaces (except the openbmc/pyphosphor, but we have removed support for python) should have been removed, so drop the support for the old interface here. Partially resolves openbmc/openbmc#3584 In addition, when I commited this change, ci reported code format error: @libmapper/mapper.h -int mapper_wait_async(sd_bus*, sd_event*, char* [], void (*)(int, void*), void*, +int mapper_wait_async(sd_bus*, sd_event*, char*[], void (*)(int, void*), void*, Fixed that. Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I0c2d0458a3f55f4671b91f6492e7218ecc3df4aa
|
/openbmc/phosphor-objmgr/src/test/ |
H A D | interfaces_added.cpp | d0cf9428 Tue Sep 17 03:01:34 CDT 2019 John Wang <wangzqbj@inspur.com> Drop support for old association interface A new association interface is defined in phosphor-dbus-interfaces It would be nice to move the local version of the interface to the new one. The behavior of how association work is described here: https://github.com/openbmc/docs/blob/master/object-mapper.md#associations I did some searching and confirmed that all the old interfaces (except the openbmc/pyphosphor, but we have removed support for python) should have been removed, so drop the support for the old interface here. Partially resolves openbmc/openbmc#3584 In addition, when I commited this change, ci reported code format error: @libmapper/mapper.h -int mapper_wait_async(sd_bus*, sd_event*, char* [], void (*)(int, void*), void*, +int mapper_wait_async(sd_bus*, sd_event*, char*[], void (*)(int, void*), void*, Fixed that. Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I0c2d0458a3f55f4671b91f6492e7218ecc3df4aa
|
/openbmc/phosphor-objmgr/src/ |
H A D | processing.hpp | d0cf9428 Tue Sep 17 03:01:34 CDT 2019 John Wang <wangzqbj@inspur.com> Drop support for old association interface A new association interface is defined in phosphor-dbus-interfaces It would be nice to move the local version of the interface to the new one. The behavior of how association work is described here: https://github.com/openbmc/docs/blob/master/object-mapper.md#associations I did some searching and confirmed that all the old interfaces (except the openbmc/pyphosphor, but we have removed support for python) should have been removed, so drop the support for the old interface here. Partially resolves openbmc/openbmc#3584 In addition, when I commited this change, ci reported code format error: @libmapper/mapper.h -int mapper_wait_async(sd_bus*, sd_event*, char* [], void (*)(int, void*), void*, +int mapper_wait_async(sd_bus*, sd_event*, char*[], void (*)(int, void*), void*, Fixed that. Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I0c2d0458a3f55f4671b91f6492e7218ecc3df4aa
|
H A D | processing.cpp | d0cf9428 Tue Sep 17 03:01:34 CDT 2019 John Wang <wangzqbj@inspur.com> Drop support for old association interface A new association interface is defined in phosphor-dbus-interfaces It would be nice to move the local version of the interface to the new one. The behavior of how association work is described here: https://github.com/openbmc/docs/blob/master/object-mapper.md#associations I did some searching and confirmed that all the old interfaces (except the openbmc/pyphosphor, but we have removed support for python) should have been removed, so drop the support for the old interface here. Partially resolves openbmc/openbmc#3584 In addition, when I commited this change, ci reported code format error: @libmapper/mapper.h -int mapper_wait_async(sd_bus*, sd_event*, char* [], void (*)(int, void*), void*, +int mapper_wait_async(sd_bus*, sd_event*, char*[], void (*)(int, void*), void*, Fixed that. Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I0c2d0458a3f55f4671b91f6492e7218ecc3df4aa
|
H A D | main.cpp | d0cf9428 Tue Sep 17 03:01:34 CDT 2019 John Wang <wangzqbj@inspur.com> Drop support for old association interface A new association interface is defined in phosphor-dbus-interfaces It would be nice to move the local version of the interface to the new one. The behavior of how association work is described here: https://github.com/openbmc/docs/blob/master/object-mapper.md#associations I did some searching and confirmed that all the old interfaces (except the openbmc/pyphosphor, but we have removed support for python) should have been removed, so drop the support for the old interface here. Partially resolves openbmc/openbmc#3584 In addition, when I commited this change, ci reported code format error: @libmapper/mapper.h -int mapper_wait_async(sd_bus*, sd_event*, char* [], void (*)(int, void*), void*, +int mapper_wait_async(sd_bus*, sd_event*, char*[], void (*)(int, void*), void*, Fixed that. Signed-off-by: John Wang <wangzqbj@inspur.com> Change-Id: I0c2d0458a3f55f4671b91f6492e7218ecc3df4aa
|