search for: r006

...ever done such a thing? Thx for advice, Regards, Philippe __________________________________________________ Philippe Lamote Technology Lead @TSSC - Johnson & Johnson Pharmaceutical R&D <Software Architect && System Design/> <Tel (32 +14)60-5735 | Loc: Beerse-1 ~ B073-R006/>

...patible-function-type | `-- lib-kunit-test.c:warning:cast-from-void-(-)(const-void-)-to-kunit_action_t-(aka-void-(-)(void-)-)-converts-to-incompatible-function-type |-- i386-randconfig-i011-20230703 | `-- drivers-bluetooth-btmtk.c:error:no-member-named-dump-in-struct-hci_dev `-- s390-randconfig-r006-20230704 |-- lib-kunit-executor_test.c:warning:cast-from-void-(-)(const-void-)-to-kunit_action_t-(aka-void-(-)(void-)-)-converts-to-incompatible-function-type `-- lib-kunit-test.c:warning:cast-from-void-(-)(const-void-)-to-kunit_action_t-(aka-void-(-)(void-)-)-converts-to-incompatible-funct...

...randconfig-r041-20230731 clang hexagon randconfig-r045-20230731 clang i386 allyesconfig gcc i386 buildonly-randconfig-r004-20230731 gcc i386 buildonly-randconfig-r005-20230731 gcc i386 buildonly-randconfig-r006-20230731 gcc i386 debian-10.3 gcc i386 defconfig gcc i386 randconfig-i001-20230731 gcc i386 randconfig-i002-20230731 gcc i386 randconfig-i003-20230731 gcc i386...

Hi all, The goal of the series is to give a chance to the architecture to validate VIRTIO device features. The tests are back to virtio_finalize_features. No more argument for the architecture callback which only reports if the architecture needs guest memory access restrictions for VIRTIO. I renamed the callback to arch_has_restricted_virtio_memory_access, the config option to

Hi all, The goal of the series is to give a chance to the architecture to validate VIRTIO device features. The tests are back to virtio_finalize_features. No more argument for the architecture callback which only reports if the architecture needs guest memory access restrictions for VIRTIO. I renamed the callback to arch_has_restricted_virtio_memory_access, the config option to