virutil: Rework how 'udevadm settle' is called

[libvirt] [PATCH 0/4] virutil: Rework how 'udevadm settle' is called

Michal Privoznik posted 4 patches 4 years, 11 months ago

Download series mbox

Test syntax-check passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/cover.1558086709.git.mprivozn@redhat.com

m4/virt-external-programs.m4 | 26 +++++++-------------------
src/util/virutil.c           | 20 ++++++--------------
2 files changed, 13 insertions(+), 33 deletions(-)

Expand all Fold all

[libvirt] [PATCH 0/4] virutil: Rework how 'udevadm settle' is called

Posted by Michal Privoznik 4 years, 11 months ago

Apparently, some build systems have a very minimalistic approach to
their default build root. Not even udevadm is there. This renders our
virWaitForDevices() to be no-op. But with this rework we can still run
udevadm settle just fine with no extra build dependency added.

Michal Prívozník (4):
  virWaitForDevices: Drop untrue part of comment
  lib: Drop UDEVSETTLE
  m4: Provide default value fore UDEVADM
  m4: Drop needless string checks

 m4/virt-external-programs.m4 | 26 +++++++-------------------
 src/util/virutil.c           | 20 ++++++--------------
 2 files changed, 13 insertions(+), 33 deletions(-)

-- 
2.21.0

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list