[PATCH 06/33] virCPUx86DataParse: Don't check error from x86FeatureNames

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



x86FeatureNames uses virBuffer and thus can't fail nowadays.

Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx>
---
 src/cpu/cpu_x86.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/src/cpu/cpu_x86.c b/src/cpu/cpu_x86.c
index 92f945beb4..79c5868ae6 100644
--- a/src/cpu/cpu_x86.c
+++ b/src/cpu/cpu_x86.c
@@ -1856,11 +1856,7 @@ virCPUx86DataParse(xmlXPathContextPtr ctxt)
  */
 #define virX86CpuIncompatible(MSG, CPU_DEF) \
         do { \
-            g_autofree char *flagsStr = NULL; \
-            if (!(flagsStr = x86FeatureNames(map, ", ", (CPU_DEF)))) { \
-                virReportOOMError(); \
-                return VIR_CPU_COMPARE_ERROR; \
-            } \
+            g_autofree char *flagsStr = x86FeatureNames(map, ", ", (CPU_DEF)); \
             if (message) \
                 *message = g_strdup_printf("%s: %s", _(MSG), flagsStr); \
             VIR_DEBUG("%s: %s", MSG, flagsStr); \
-- 
2.29.2




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux