[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child
|
From: |
Philippe Mathieu-Daudé |
|
Subject: |
Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description |
|
Date: |
Mon, 29 Jun 2020 13:38:00 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 |
On 6/27/20 8:55 AM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>
>> 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
>
> Please show us output of "info qom-tree" before and after. Feel free to
> cut uninteresting parts.
>
For 'info qom-tree' this is a one-line change, because ram_memdev
is not displayed in it:
/machine (sam460ex-machine)
/peripheral (container)
/peripheral-anon (container)
/unattached (container)
- /device[2] (smbus-eeprom)
- [RFC PATCH 2/3] hw/i2c/smbus_eeprom: Add description based on child name, (continued)
- [RFC PATCH 2/3] hw/i2c/smbus_eeprom: Add description based on child name, Philippe Mathieu-Daudé, 2020/06/26
- [RFC PATCH 3/3] hw/i2c/smbus_eeprom: Trace reset() event, Philippe Mathieu-Daudé, 2020/06/26
- Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description, no-reply, 2020/06/26
- Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description, no-reply, 2020/06/26
- Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description, Aleksandar Markovic, 2020/06/26
- Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description, Markus Armbruster, 2020/06/27
- Re: [RFC PATCH 0/3] Use object_get_canonical_path_component to get child description,
Philippe Mathieu-Daudé <=