Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description

[Philippe Mathieu-Daudé]

On 6/26/20 5:59 PM, Aleksandar Markovic wrote:
> пет, 26. јун 2020. у 12:27 Philippe Mathieu-Daudé <f4bug@amsat.org> је
> написао/ла:
>>
>> This RFC is simply a proof-of-concept to see if I correctly
>> understood Markus' suggestion, see the thread around:
>> https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg08652.html
>>
>> Philippe Mathieu-Daudé (3):
>>   hw/i2c/smbus_eeprom: Set QOM parent
>>   hw/i2c/smbus_eeprom: Add description based on child name
>>   hw/i2c/smbus_eeprom: Trace reset() event
>>
>>  include/hw/i2c/smbus_eeprom.h |  9 ++++++---
>>  hw/i2c/smbus_eeprom.c         | 18 +++++++++++++++---
>>  hw/mips/fuloong2e.c           |  2 +-
>>  hw/ppc/sam460ex.c             |  2 +-
>>  hw/i2c/trace-events           |  3 +++
>>  5 files changed, 26 insertions(+), 8 deletions(-)
>>
>> --
> 
> Is there any documentation related to this interface? If yes, provide
> the link, and describe what is not clear to you. If not, then this
> series should provide appropriate documentation.

It is described in "qom/object.h":

/**
 * object_get_canonical_path_component:
 *
 * Returns: The final component in the object's canonical path.  The
canonical
 * path is the path within the composition tree starting from the root.
 * %NULL if the object doesn't have a parent (and thus a canonical path).
 */
char *object_get_canonical_path_component(const Object *obj);

> 
> In times we desperately need working "Continuous Integration", it
> looks we instead spend our time on "Continuous Interface Guessing" -
> for years.
> 
> Thanks,
> Aleksandar
> 
> 
> 
>> 2.21.3
>>
>