Re: [libvirt] [PATCH] tests: Only format the CPU frequency if it's known

2018-01-09 Thread John Ferlan
On 01/09/2018 04:06 AM, Andrea Bolognani wrote: > On Mon, 2018-01-08 at 11:19 -0500, John Ferlan wrote: >> On 01/08/2018 09:50 AM, Peter Krempa wrote: >>> On Mon, Jan 08, 2018 at 15:10:29 +0100, Andrea Bolognani wrote: Instead of formatting 'MHz: 0', which can be confusing, skip the fie

Re: [libvirt] [PATCH] tests: Only format the CPU frequency if it's known

2018-01-09 Thread Andrea Bolognani
On Mon, 2018-01-08 at 11:19 -0500, John Ferlan wrote: > On 01/08/2018 09:50 AM, Peter Krempa wrote: > > On Mon, Jan 08, 2018 at 15:10:29 +0100, Andrea Bolognani wrote: > > > Instead of formatting 'MHz: 0', which can be confusing, skip the > > > field altogether. This behavior is consistent with tha

Re: [libvirt] [PATCH] tests: Only format the CPU frequency if it's known

2018-01-08 Thread John Ferlan
On 01/08/2018 09:50 AM, Peter Krempa wrote: > On Mon, Jan 08, 2018 at 15:10:29 +0100, Andrea Bolognani wrote: >> Instead of formatting 'MHz: 0', which can be confusing, skip the >> field altogether. This behavior is consistent with that of 'virsh >> nodeinfo'. >> >> Suggested-by: John Ferlan >>

Re: [libvirt] [PATCH] tests: Only format the CPU frequency if it's known

2018-01-08 Thread Peter Krempa
On Mon, Jan 08, 2018 at 15:10:29 +0100, Andrea Bolognani wrote: > Instead of formatting 'MHz: 0', which can be confusing, skip the > field altogether. This behavior is consistent with that of 'virsh > nodeinfo'. > > Suggested-by: John Ferlan > Signed-off-by: Andrea Bolognani > --- > .../linux-a

[libvirt] [PATCH] tests: Only format the CPU frequency if it's known

2018-01-08 Thread Andrea Bolognani
Instead of formatting 'MHz: 0', which can be confusing, skip the field altogether. This behavior is consistent with that of 'virsh nodeinfo'. Suggested-by: John Ferlan Signed-off-by: Andrea Bolognani --- .../linux-aarch64-f21-mustang.expected | 2 +- .../linux-aarch64-rhel74-moonsh